group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1714505@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package debian-installer-utils -
1.113ubuntu1.16.04.1

---------------
debian-installer-utils (1.113ubuntu1.16.04.1) xenial; urgency=medium

  * Make sure udevd internal state is up-to-date before calling trigger &
    settle. This insures that newly anna-installed udev rules and kernel
    modules are loaded by udevd for correct processing of the udev
    rules. LP: #1714505.

 -- Dimitri John Ledkov <xnox@xxxxxxxxxx>  Sun, 17 Sep 2017 00:41:44
+0100

** Changed in: debian-installer-utils (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1714505

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in debian-installer-utils package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  In Progress
Status in debian-installer-utils source package in Trusty:
  In Progress
Status in debian-installer source package in Xenial:
  New
Status in debian-installer-utils source package in Xenial:
  Fix Released
Status in debian-installer source package in Zesty:
  In Progress
Status in debian-installer-utils source package in Zesty:
  Fix Released
Status in debian-installer source package in Artful:
  Fix Released
Status in debian-installer-utils source package in Artful:
  Fix Released

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not including nvme module
  -udevd starts, and creates its kmod module context, which does not include nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  The fix is to reload udevadm rules, as per upstream recommendation.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  Stale context in udevd is expected, and one is supposed to reload
  rules via udevadm, which is the fix proposed in debian-installer-
  utils. Removing the previous second test case that does not reload via
  udevadm.

  [Regression Potential]

  Additional calls to udevadm reload will cause all udev rules to be re-
  read correctly. This may lead to new devices
  discovered/configured/symlink during d-i installer, which were
  previously skipped/missed.

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