[LTS] cryptsetup-initramfs fails when kernel modules are compressed

Bug #2057808 reported by TJ
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Fix Released
Critical
Unassigned
Jammy
New
Critical
Unassigned
linux (Ubuntu)
Invalid
Critical
Unassigned
Jammy
Won't Fix
Medium
Unassigned

Bug Description

This is the same cause as the Mantic bug "cryptsetup autopkgtest fails with zstd compressed kernel modules"

https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2035120

where hooks/cryptroot::add_modules() needs postfix wildcards after $glob.ko on 2 lines.

It affects 22.04 LTS with recent kernel or local kernel built with CONFIG_MODULE_COMPRESS_*

I think the fix needs cherry-picking into LTS release(s).

https://salsa.debian.org/cryptsetup-team/cryptsetup/-/commit/8359ad85a541b76f388cdc28f549229e3d71e750

At boot-time it results in the cryptic (pun intended) messages:

device-mapper: table: 253:0 crypt: Error allocating crypto tfm (-ENOENT)
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl on luks_os (253:0) failed: No such file or directory

TJ (tj)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

It is not clear that this is a behavior change in the kernel that should have been included as part of the hwe backports. cryptsetup may not be the only package affected.

Changed in linux (Ubuntu):
importance: Undecided → Critical
Changed in cryptsetup (Ubuntu):
importance: Undecided → Critical
Changed in cryptsetup (Ubuntu Jammy):
importance: Undecided → Critical
Changed in cryptsetup (Ubuntu):
status: New → Fix Released
Changed in linux (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu Jammy):
importance: Undecided → Critical
Revision history for this message
Steve Langasek (vorlon) wrote :

You say "recent kernel or local kernel." What Ubuntu-provided kernel for Ubuntu 22.04 LTS do you see this with?

Changed in linux (Ubuntu Jammy):
status: New → Incomplete
Revision history for this message
TJ (tj) wrote :

Recent kernels: 6.8.0-25 from Noble and the mainline kernel builds from e.g:

https://kernel.ubuntu.com/mainline/v6.8/amd64/

Used for ensuring support for recent hardware.

If these will be rebuilt without module compression for LTS/HWE kernel releases then this issue isn't so vital, but it will make testing a recent kernel (often asked for when hitting hardware/kernel issues) extremely challenging and for most non-technical operators, impossible.

On balance I'd think adding those two wildcards is a win.

Revision history for this message
Stefan Bader (smb) wrote :

Mainline was and is nothing really supported. They are there because they help debugging (instead of doing bisect builds). When we do official hwe kernels they get built without module compression (going to Jammy). When doing your own backports ensure you have "jammy" as the target in the current changelog section (not UNRELEASED or noble).

Changed in linux (Ubuntu Jammy):
status: Incomplete → Won't Fix
importance: Critical → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.