Bug 360441

Summary:	kernel dm: some dm ioctl can fail with 32bit userspace and 64bit kernel
Product:	Red Hat Enterprise Linux 5	Reporter:	Milan Broz <mbroz>
Component:	kernel	Assignee:	Milan Broz <mbroz>
Status:	CLOSED ERRATA	QA Contact:	Martin Jenner <mjenner>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.0	CC:	agk, dwysocha, pvrabec
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHBA-2008-0314	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-21 14:59:58 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 Milan Broz 2007-10-31 15:29:05 UTC

Description of problem:

DM-ioctl structure on 32bit on i386 arch has size 308 bytes,
on x86_64 312 bytes.

Some dm ioctl can then fail because of align check in kernel:

/dmsetup.static.32.rhel -vv message mpath 0 fail_if_no_path
dm version   OF   [16384]
dm message mpath  OF  fail_if_no_path [16384]
device-mapper: message ioctl failed: Invalid argument
Command failed

Because dm processing uses own code to checks validity of ioctl struct,
fix can be backported without changing kABI.

Comment 1 RHEL Program Management 2007-10-31 15:35:31 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 4 Don Zickus 2008-01-08 20:46:41 UTC

in 2.6.18-64.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Comment 7 errata-xmlrpc 2008-05-21 14:59:58 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-0314.html