| commit | 554962405cb18a3e624edf05b6257eaf9273810c | |
| author | Mark McLoughlin <markmc@redhat.com> | |
| Fri, 3 Jul 2009 08:28:02 +0000 (3 09:28 +0100) | ||
| committer | Anthony Liguori <aliguori@us.ibm.com> | |
| Fri, 10 Jul 2009 18:44:29 +0000 (10 13:44 -0500) | ||
| tree | 7c4d9cb4ddbd6dba78ed67cecc10dd892b819438 | treesnapshot (tar.gz zip) |
| parent | 1fa63e43e64596455938e09d3e6ec89eb0c4bbc8 | commitdiff |
Prefer sysfs for USB host devices
Scanning for devices via /sys/bus/usb/devices/ and using them via the
/dev/bus/usb/<bus>/<device> character devices is the prefered method
on modern kernels, so try that first.
When using SELinux and libvirt, qemu will have access to /sys/bus/usb
but not /proc/bus/usb, so although the current code will work just
fine, it will generate SELinux AVC warnings.
See also:
https://bugzilla.redhat.com/508326
Reported-by: Daniel Berrange <berrange@redhat.com>
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Scanning for devices via /sys/bus/usb/devices/ and using them via the
/dev/bus/usb/<bus>/<device> character devices is the prefered method
on modern kernels, so try that first.
When using SELinux and libvirt, qemu will have access to /sys/bus/usb
but not /proc/bus/usb, so although the current code will work just
fine, it will generate SELinux AVC warnings.
See also:
https://bugzilla.redhat.com/508326
Reported-by: Daniel Berrange <berrange@redhat.com>
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
| usb-linux.c | diffblobblamehistory |