Red Hat Bugzilla – Bug 158819
RHEL3 does not support USBDEVFS 32-bit ioctls on x86_64
Last modified: 2007-11-30 17:07:07 EST
Escalated to Bugzilla from IssueTracker
PM ACK for U6
Created attachment 115382 [details]
Candidate #1 - not using set_fs()
Same as in bug 158852, only somewhat lighter touch than RHEL 4:
- All definitions are in the drivers/usb/devio.c
- Uses CONFIG_IA32_EMULATION instead of CONFIG_COMPAT
Created attachment 120109 [details]
Candidate #2 - added COMPATIBLE_IOCTL
I need Dell to test the kernel from this URL:
The patch seems simple, but we always test actual patch and actual build,
just in case of a typo somewhere.
Fixing "hardware" field and putting into NEEDINFO state.
Please test PeteZ's fix as requested in comment #20.
I don't see any bugzilla comment verifying that the testing was completed
successfully (as requested in comment #20). Reverting to NEEDINFO.
A fix for this problem has just been committed to the RHEL3 U7
patch pool this evening (in kernel version 2.4.21-37.11.EL).
Public Bug. All future communication should occur in this bug 158819.
Event posted 02-07-2006 12:45am by Byju_Michael
not fixed in RHEL3 U7
It totally was fixed. What is the actual kernel release which prompted the
comment by Byju? How did they test? And come to think about it, nobody
acted upon my request to test (comment #20) and Ernie's reminders.
Event posted 02-15-2006 06:22am by Byju_Michael
This is regressed with RHEL 3 U7 post beta1 kernel 2.4.21-40.EL kernel and the
issue is fixed.
Charles Rose, please clarify your last comment. I don't understand
what you meant by "regressed". As far as I know, this problem was
fixed in U7 before the beta candidate (-38.EL) was built and it
remains fixed in the most recent U7 respin (-40.EL).
Thanks in advance. -ernie
Sorry for the confusion. The issue was fixed in -38.EL and was verified again
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.