[Bug 925122] Re: container's udevadm trigger --add affects the host

[Serge Hallyn]

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
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/925122

Title:
  container's udevadm trigger --add affects the host

Status in “lxc” package in Ubuntu:
  Confirmed
Status in “udev” package in Ubuntu:
  Confirmed

Bug description:
  When the container does 'udevadm trigger --add' (in
  /etc/init/udevtrigger.conf), the host re-processes all those events
  too.  This can lead (less importantly) to keyboard settings and
  soundcard levels being reset, but (more importantly) could presumably
  also cause worse troubles.

  Once upstart has a concept of being ina  container, udev should be
  updated to not run udevtrigger.conf when in a container.

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