Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 446962

Summary: Access to firewire devices is still allowed after the device is removed from the bus.
Product: Red Hat Enterprise Linux 5 Reporter: Jay Fenlason <fenlason>
Component: kernelAssignee: Jay Fenlason <fenlason>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: low Docs Contact:
Priority: low    
Version: 5.2CC: dzickus, jfeeney
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 20:22:49 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:
Attachments:
Description Flags
Patch against 2.6.25 none

Description Jay Fenlason 2008-05-16 19:20:25 UTC 
Description of problem:
When userspace has opened a firewire device, and then the device is removed 
from the bus, userspace can still attempt to send requests to the device.  If 
userspace guesses the correct generation, the request will go to a different 
device.

Version-Release number of selected component (if applicable):
2.6.18-92.el5

How reproducible:
Always

Steps to Reproduce:
1.Attach a firewire camera to the system.
2.Have a program open /dev/fw1 (or whatever the camera's device is).
3.Unplug the camera
4.Send a ReadQuadletRequest to the device, using the new generation
5.Observe that you get a response back from a different device.
  
Actual results:
Userspace is still allowed to make requests.  They go to a different device.

Expected results:
Userspace should get ENODEV.

Additional info:
Recently fixed upstream, but I don't have the commit to hand.
Comment 1 Jay Fenlason 2008-05-16 19:25:39 UTC 
Created attachment 305728 [details]
Patch against 2.6.25
Comment 2 RHEL Program Management 2008-05-16 19:41:55 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 3 Stefan Richter 2008-06-01 09:25:04 UTC 
upstream commit is 551f4cb9de716ffcdaf968c99a450c22ff12e8c3 post 2.6.26-rc3
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=551f4cb9de716ffcdaf968c99a450c22ff12e8c3
Comment 7 Don Zickus 2008-09-16 15:15:05 UTC 
This fix should be included in the latest RHEL-5 kernel which can be found here:
http://people.redhat.com/dzickus/el5
Comment 12 errata-xmlrpc 2009-01-20 20:22:49 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 therefore 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/RHSA-2009-0225.html