Bug 638801
Summary: | SELinux está negando a /usr/bin/qemu-kvm el acceso "read" on /dev/bus/usb/001/004 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Juan Urroa <observer1> | ||||||||
Component: | libvirt | Assignee: | Daniel Veillard <veillard> | ||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | low | ||||||||||
Version: | 13 | CC: | berrange, clalance, crobinso, dwalsh, gui1ty, itamar, jforbes, mgrepl, mma.priv, veillard, virt-maint | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | setroubleshoot_trace_hash:d64227b1431185ca4dc453d038c77a12b2c516591ba4b9a8b07baa6e0be277c8 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2011-06-06 07:21:13 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
Juan Urroa
2010-09-30 00:44:29 UTC
This would either be an issue with libvirt or udev. There are two other related SELinux alerts about "ioctl" and "read write" access which both lead to bug #537227 which has been closed. I asked for it to be re-opened. All of the alerts come down to the same thing, the device is mislabeled, so svirt_t can not read/write/ioctl/getattr .. the device. So either libvirt did not set the label on the device, or udev changed the label on the device back to the default. Created attachment 469198 [details]
kernel messages
After having attached the device and the usual auto mount kicking in the devices in /dev/bus/usb/002/ are of type usb_device_t.
When I attach the device to a guest and subsequently turn the vm on I see the label very briefly change to svirt_image_t, just for the whole device to disappear a second later and a new device appearing which receives type usb_device_t again.
This seems odd to me. It appears libvirt is disconnecting (ejecting?) the device.
See attachment for what /var/log/messages tells me during the full cycle (from plugging in the physical hardware to booting (all in permissive mode, btw).
Created attachment 469448 [details]
ioctl denial
Created attachment 469449 [details]
read write denial
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |