[Bug 1103022] Re: 70-udev-acl.rules needs to put g+rw on /dev/kvm

[Serge Hallyn]

Can you please try that a few more times?  If I script that, I find that
I get your results if I don't put a sleep before the udevadm trigger,
but the right results if I do.  I.e.:

cat > kvmudevtest << EOF
mv /lib/udev/rules.d/40-qemu-system.rules{,.disabled}
mv /lib/udev/udev-acl{,.disabled}
rmmod kvm_intel
modprobe kvm_intel
cp /lib/udev/rules.d/40-qemu-system.rules{.disabled,}
sleep 2
udevadm trigger --sysname-match=kvm  --verbose
ls -l /dev/kvm
EOF

bash kvmudevtest

with the sleep, it works.  Without the sleep, /dev/kvm does not get
chowned.  (obviously just a race with inotify and udev's handling
thereof)

So disabling udev-acl, on my raring test system, gives just the
right result.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/1103022

Title:
  70-udev-acl.rules needs to put g+rw on /dev/kvm

Status in “udev” package in Ubuntu:
  Confirmed

Bug description:
  When qemu-system gets installed, the newly installed udev rule causes
  /dev/kvm to gets chgrpd to kvm and its mode to get set to g+rw.
  However, because /dev/kvm was tagged with ACL previously, there is a
  group:: acl on /dev/kvm which does not get removed.  Therefore
  /dev/kvm is g+rw in the file mode, but the acl denies group read/write
  access.  After a reboot all is fine.

  I have not seen a clean way to have udev remove that acl, and there is
  no reason for it.  So please update the 70-udev-acl.rules file to set
  MODE=0660 on /dev/kvm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1103022/+subscriptions