lttng team mailing list archive

[Łukasz Zemczak <1914279@xxxxxxxxxxxxxxxxxx>]

** Also affects: acpi-call (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: backport-iwlwifi-dkms (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: bcmwl (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: dahdi-linux (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: dm-writeboost (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: evdi (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: gost-crypto (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: iptables-netflow (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: liblzf (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: lime-forensics (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: lttng-modules (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: openafs (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: oss4 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: r8168 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: rtl8812au (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: sysdig (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: v4l2loopback (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: virtualbox (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: virtualbox-hwe (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: zfs-linux (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
LTTng, which is subscribed to lttng-modules in Ubuntu.
Matching subscriptions: lttng-modules-bugs
https://bugs.launchpad.net/bugs/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in bcmwl package in Ubuntu:
  New
Status in dahdi-linux package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  New
Status in evdi package in Ubuntu:
  New
Status in gost-crypto package in Ubuntu:
  New
Status in iptables-netflow package in Ubuntu:
  New
Status in liblzf package in Ubuntu:
  New
Status in lime-forensics package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-meta package in Ubuntu:
  Triaged
Status in lttng-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in r8168 package in Ubuntu:
  New
Status in rtl8812au package in Ubuntu:
  New
Status in sysdig package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New
Status in virtualbox-hwe package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot..... which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions