This bug is awaiting verification that the linux-
hwe-5.19/5.19.0-24.25~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-5.19 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991664

Title:
  backport dkms fixes to build modules correctly for hwe-5.19+ kernels
  with custom compiler

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in ipu6-drivers package in Ubuntu:
  New
Status in ivsc-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in backport-iwlwifi-dkms source package in Jammy:
  New
Status in dkms source package in Jammy:
  Fix Released
Status in ipu6-drivers source package in Jammy:
  New
Status in ivsc-driver source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in v4l2loopback source package in Jammy:
  New
Status in zfs-linux source package in Jammy:
  New

Bug description:
  [ Impact ]

   * hwe-5.19 kernel has to be compiled with gcc-12+ for the new
  security kernel config options that have been enabled in that kernel
  (init zero structs).

   * dkms needs to be patched to attempt to use the same compiler as was
  used to build the kernel, specifically use gcc for v5.15 but gcc-12
  for v5.19+ in jammy

   * dkms autopkgtests also need to be improved to ensure there are no
  false negatives when kernel has module under test already built-in at
  the same version.

   * because linux-headers packages in Ubuntu do not depend on a
  toolchain, and it is very hard to correctly depend on a native or
  cross-toolchain, add gcc-12 dependency in the dkms package.

  [ Test Plan ]

   * Retrigger dkms module test for a built-in package of the same
  version as already built into the kernel, for example zfs-linux dkms.
  It should pass.

   * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel
  from proposed. dkms module should be built with gcc and gcc-12
  respectively.

  [ Where problems could occur ]

   * New gcc-12 dependency on the dkms package may result in two
  compilers being installed in the Ubuntu Desktop Live image

   * New gcc-12 dependency may prevent automatic upgrade/installation of
  the dkms package update via unattended upgrades.

  [ Other Info ]

   * It is questionable for dkms to depend on any c-compiler, given that
  a module for a given kernel can really be built with the same
  toolchain and the same compiler features.

   * In debian, linux kernel packages ship and extra configuration file
  in the kernel headers, dkms uses said configuration file to use a
  matching compiler, and linux-headers packages depend on the toolchain
  used to build a given kernel. Maybe in the future Ubuntu could
  consider using the same packaging.

   * Some DKMS modules need further fixes to preserve and not loose the
  compiler setting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to