Red Hat Bugzilla – Bug 668478
PCI sysfs rom file needs owner write access
Last modified: 2013-01-09 18:28:30 EST
Description of problem: The PCI sysfs rom file is mode 0400, but it's usage requires writing 1/0 to enable/disable the rom around reads. This causes problems for KVM device assignment, which wants to allow a de-privileged qemu instance to open the file R/W to extract the contents. libvirt gives qemu ownership of the file, but the mode is wrong for the required usage. Version-Release number of selected component (if applicable): kernel-2.6.32-71.4.1.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Give a normal user ownership of the pci sysfs file (/sys/bus/pci/devices/ssss:bb:dd.f/rom) 2. Try to read the rom contents (echo 1 >$ROMFILE; cat $ROMFILE) 3. Actual results: cannot read Expected results: owner of the file is able to access contents per API Additional info:
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.
Patch(es) available on kernel-2.6.32-112.el6
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-2011-0542.html