Bug 437496

Summary:	libdlm copies lvb from bad address
Product:	Red Hat Enterprise Linux 5	Reporter:	David Teigland <teigland>
Component:	cman	Assignee:	David Teigland <teigland>
Status:	CLOSED ERRATA	QA Contact:	GFS Bugs <gfs-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.2	CC:	ccaulfie, cluster-maint, djansa, edamato, rkenna
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2008-0347	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-21 15:58:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Teigland 2008-03-14 16:05:07 UTC

Description of problem:

When a program does a lock operation that reads an lvb, libdlm
copies the lvb data from a bogus location instead of from the
proper offset in the buffer it just read.  The location of the
lvb data is calculated wrongly due to a missing cast.

This causes a segfault in the program.  This was introduced by
the libdlm changes that went into 5.2.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2008-03-18 15:30:30 UTC

This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

Comment 5 David Teigland 2008-03-20 17:33:19 UTC

pushed to RHEL5 branch 1bb513e542a4ca7f3e79f5000b0bb0783a41b0b5

Comment 7 Dean Jansa 2008-03-27 15:19:27 UTC

With this patch I am able to read/write lvbs without issue.

Comment 9 errata-xmlrpc 2008-05-21 15:58:56 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0347.html