Red Hat Bugzilla – Bug 446962
Access to firewire devices is still allowed after the device is removed from the bus.
Last modified: 2014-08-31 19:28:53 EDT
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.
Created attachment 305728 [details] Patch against 2.6.25
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.
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
This fix should be included in the latest RHEL-5 kernel which can be found here: http://people.redhat.com/dzickus/el5
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