[Bug 1297248] Re: Wait timeout for systemd-udevd worker process is too short

[Martin Pitt]

Can you please explain in more detail (perhaps with an example) how the
kthread_create() change affects the killing of RUN/IMPORT rules? udev
has always behaved that way to guard against hanging RUN programs. The
boot can take much longer than 30 seconds, just every single RUN action
should be much, much faster (otherwise it's written in a wrong way). In
fact I consider 30 seconds way too overgenerous.

Thanks!

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

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

Title:
  Wait timeout for systemd-udevd worker process is too short

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  Coming from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705 .

  Commit 786235ee in the upstream kernel made kthread_create() return
  immediately upon SIGKILL. On several machines, device initialization
  phase takes more than 30 seconds before kthread_create() is called.

  Since systemd-udevd unconditionally sends SIGKILL upon hardcoded 30
  seconds timeout, boot is failing upon such machines. The conclusion
  of LKML discussion seems that we should fix systemd-udevd side
  rather than fixing kthread_create() side because hardcoded 30 seconds
  timeout is considered as a bug of systemd. Therefore, please consider
  allowing configurable (or at least much longer) timeout for
  systemd-udevd worker process.

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