[Bug 925122] Re: container's udevadm trigger --add affects the host
This bug was fixed in the package udev - 175-0ubuntu5 --- udev (175-0ubuntu5) precise; urgency=low [ David Henningsson ] * Remove jack-detection.patch: Now that PulseAudio uses the new jack detection interface, we can remove this patch. [ Stéphane Graber ] * debian/udev.udevtrigger.upstart: Update to wait for 'container' or 'not-container' to be emitted, then skip just exit 0 but still run post-stop if it's a container and run 'udevadm trigger' if it's not. This is needed until we have a proper device namespace preventing udev events from affecting the outside. (LP: #925122) * Make udev depend on upstart >= 1.4-0ubuntu6 to ensure the next reboot will indeed either emit container or not-container. -- Stephane GraberFri, 17 Feb 2012 15:40:47 -0500 ** Changed in: udev (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925122 Title: container's udevadm trigger --add affects the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925122] Re: container's udevadm trigger --add affects the host
I applied the change to our packaging branch for udev but didn't upload yet as the new upstart failed to build on armel, armhf and powerpc. Uploading the change with the current upstart would most likely break if not slow down the boot. ** Changed in: udev (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: udev (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925122 Title: container's udevadm trigger --add affects the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925122] Re: container's udevadm trigger --add affects the host
wrapping lxc-start confirms umask is 0077 when lxc-start is called through juju. ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925122 Title: container's udevadm trigger --add affects the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925122] Re: container's udevadm trigger --add affects the host
(please feel free to re-mark confirmed for lxc if you disagree :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925122 Title: container's udevadm trigger --add affects the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925122] Re: container's udevadm trigger --add affects the host
In my opinion, the fix here is for juju to set its umask to 0022 before calling lxc-start -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925122 Title: container's udevadm trigger --add affects the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925122] Re: container's udevadm trigger --add affects the host
My guess is that juju is setting umask somewhere? The mode passed to mkdir(2) is &'d with the task's umask. The code in lxc definately passes 0755 as the mode. We could patch lxc to do an explicit chmod after the fact, but that seems like the wrong thing to do. The umask - ideally - was set as it was for a reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925122 Title: container's udevadm trigger --add affects the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
