Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Hi Michael, On Wed, Dec 06, 2023 at 10:54:04AM +0100, Michael Ott wrote: > Hi, > > after updating cryptsetup it works > > Thanks for that Thanks for the confirmation! Regards, Salvatore
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
On Tue, Dec 05, 2023 at 05:16:31PM +0100, Salvatore Bonaccorso wrote: > And in fact this is the solution proposed in #1036049. And we need to fix that in stable as well. Not sure if we can safely use Conflicts to make sure we have a suitable version. At least without the current apt prefering to remove cryptsetup instead and really make people's systems unbootable. Bastian -- Hailing frequencies open, Captain.
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Hi,
after updating cryptsetup it works
Thanks for that
On Tue, 2023-12-05 at 17:16 +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Tue, Dec 05, 2023 at 05:14:20PM +0100, Salvatore Bonaccorso wrote:
> > Control: reassign -1 src:cryptsetup 2:2.6.1-5
> >
> > Hi
> >
> > On Tue, Dec 05, 2023 at 04:55:58PM +0100, Salvatore Bonaccorso
> > wrote:
> > > Hi,
> > >
> > > On Tue, Dec 05, 2023 at 04:38:19PM +0100, Salvatore Bonaccorso
> > > wrote:
> > > > Control: tags -1 + confirmed
> > > >
> > > > On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote:
> > > > > Package: src:linux
> > > > > Version: 6.6.4-1~exp1
> > > > > Severity: important
> > > > >
> > > > > Dear Maintainer,
> > > > >
> > > > > After updating to the 6.6 kernel the password for my
> > > > > encryption does not longer
> > > > > work
> > > > >
> > > > > Please unlock disk nvme0n1p3_crypt: **
> > > > > device-mapper: table: 253:0: crypt: Error allocation crypto
> > > > > tfm (_ENOENT)
> > > > > device-mapper: ioctl: error adding target to table
> > > > > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0)
> > > > > failed: No such file or
> > > > > directory
> > > > > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad
> > > > > password or options?
> > > > >
> > > > > Everything works with 6.5. I also downgrade systemd and
> > > > > cryptosetup but no
> > > > > changes
> > > >
> > > > I suspect this is related to changes around
> > > > https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01
> > > > (but not verified, nor tracked down).
> > >
> > > Actually after a more closer look on what is in the initrd:
> > > Bastian
> > > can be this due to switching to compressed modules? If this claim
> > > is
> > > correct then likely initramfs-tools would not copy them to the
> > > initrd.
> >
> > It looks that we only consider *.ko uncompressed in
> > debian/initramfs/hooks/cryptroot:
> >
> > add_modules() {
> > local glob="$1" found=n
> > shift
> > for mod in $(find -H "$@" -name "$glob.ko" -type f -printf
> > '%f\n'); do
> > manual_add_modules "${mod%.ko}"
> > found=y
> > done
> > [ "$found" = y ] && return 0 || return 1
> > }
> >
> > but various modules are now with 6.6.4-1~exp1 compressed:
> >
> > a relatively quick woraround would be to change the function to:
> >
> > add_modules() {
> > local glob="$1" found=n
> > shift
> > for mod in $(find -H "$@" -name "$glob.ko*" -type f -printf
> > '%f\n'); do
> > manual_add_modules "${mod%.ko*}"
> > found=y
> > done
> > [ "$found" = y ] && return 0 || return 1
> > }
> >
> > Is this the correct approach though? Which other hook functions
> > might
> > be affected by the change in linux by switching to compressed
> > modules?
>
> And in fact this is the solution proposed in #1036049.
>
> Regards,
> Salvatore
--
CU
Michael
--
,''`.
: :' : Michael Ott
`. `' e-mail: michael at k-c13 dot org
`-
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich derNutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Hi,
On Tue, Dec 05, 2023 at 05:14:20PM +0100, Salvatore Bonaccorso wrote:
> Control: reassign -1 src:cryptsetup 2:2.6.1-5
>
> Hi
>
> On Tue, Dec 05, 2023 at 04:55:58PM +0100, Salvatore Bonaccorso wrote:
> > Hi,
> >
> > On Tue, Dec 05, 2023 at 04:38:19PM +0100, Salvatore Bonaccorso wrote:
> > > Control: tags -1 + confirmed
> > >
> > > On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote:
> > > > Package: src:linux
> > > > Version: 6.6.4-1~exp1
> > > > Severity: important
> > > >
> > > > Dear Maintainer,
> > > >
> > > > After updating to the 6.6 kernel the password for my encryption does
> > > > not longer
> > > > work
> > > >
> > > > Please unlock disk nvme0n1p3_crypt: **
> > > > device-mapper: table: 253:0: crypt: Error allocation crypto tfm
> > > > (_ENOENT)
> > > > device-mapper: ioctl: error adding target to table
> > > > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such
> > > > file or
> > > > directory
> > > > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or
> > > > options?
> > > >
> > > > Everything works with 6.5. I also downgrade systemd and cryptosetup but
> > > > no
> > > > changes
> > >
> > > I suspect this is related to changes around
> > > https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01
> > > (but not verified, nor tracked down).
> >
> > Actually after a more closer look on what is in the initrd: Bastian
> > can be this due to switching to compressed modules? If this claim is
> > correct then likely initramfs-tools would not copy them to the initrd.
>
> It looks that we only consider *.ko uncompressed in
> debian/initramfs/hooks/cryptroot:
>
> add_modules() {
> local glob="$1" found=n
> shift
> for mod in $(find -H "$@" -name "$glob.ko" -type f -printf '%f\n'); do
> manual_add_modules "${mod%.ko}"
> found=y
> done
> [ "$found" = y ] && return 0 || return 1
> }
>
> but various modules are now with 6.6.4-1~exp1 compressed:
>
> a relatively quick woraround would be to change the function to:
>
> add_modules() {
> local glob="$1" found=n
> shift
> for mod in $(find -H "$@" -name "$glob.ko*" -type f -printf '%f\n'); do
> manual_add_modules "${mod%.ko*}"
> found=y
> done
> [ "$found" = y ] && return 0 || return 1
> }
>
> Is this the correct approach though? Which other hook functions might
> be affected by the change in linux by switching to compressed modules?
And in fact this is the solution proposed in #1036049.
Regards,
Salvatore
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Control: reassign -1 src:cryptsetup 2:2.6.1-5
Hi
On Tue, Dec 05, 2023 at 04:55:58PM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Tue, Dec 05, 2023 at 04:38:19PM +0100, Salvatore Bonaccorso wrote:
> > Control: tags -1 + confirmed
> >
> > On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote:
> > > Package: src:linux
> > > Version: 6.6.4-1~exp1
> > > Severity: important
> > >
> > > Dear Maintainer,
> > >
> > > After updating to the 6.6 kernel the password for my encryption does not
> > > longer
> > > work
> > >
> > > Please unlock disk nvme0n1p3_crypt: **
> > > device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT)
> > > device-mapper: ioctl: error adding target to table
> > > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such
> > > file or
> > > directory
> > > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or
> > > options?
> > >
> > > Everything works with 6.5. I also downgrade systemd and cryptosetup but no
> > > changes
> >
> > I suspect this is related to changes around
> > https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01
> > (but not verified, nor tracked down).
>
> Actually after a more closer look on what is in the initrd: Bastian
> can be this due to switching to compressed modules? If this claim is
> correct then likely initramfs-tools would not copy them to the initrd.
It looks that we only consider *.ko uncompressed in
debian/initramfs/hooks/cryptroot:
add_modules() {
local glob="$1" found=n
shift
for mod in $(find -H "$@" -name "$glob.ko" -type f -printf '%f\n'); do
manual_add_modules "${mod%.ko}"
found=y
done
[ "$found" = y ] && return 0 || return 1
}
but various modules are now with 6.6.4-1~exp1 compressed:
a relatively quick woraround would be to change the function to:
add_modules() {
local glob="$1" found=n
shift
for mod in $(find -H "$@" -name "$glob.ko*" -type f -printf '%f\n'); do
manual_add_modules "${mod%.ko*}"
found=y
done
[ "$found" = y ] && return 0 || return 1
}
Is this the correct approach though? Which other hook functions might
be affected by the change in linux by switching to compressed modules?
Regards,
Salvatore
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Hi, On Tue, Dec 05, 2023 at 04:38:19PM +0100, Salvatore Bonaccorso wrote: > Control: tags -1 + confirmed > > On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote: > > Package: src:linux > > Version: 6.6.4-1~exp1 > > Severity: important > > > > Dear Maintainer, > > > > After updating to the 6.6 kernel the password for my encryption does not > > longer > > work > > > > Please unlock disk nvme0n1p3_crypt: ** > > device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT) > > device-mapper: ioctl: error adding target to table > > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such file > > or > > directory > > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or > > options? > > > > Everything works with 6.5. I also downgrade systemd and cryptosetup but no > > changes > > I suspect this is related to changes around > https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01 > (but not verified, nor tracked down). Actually after a more closer look on what is in the initrd: Bastian can be this due to switching to compressed modules? If this claim is correct then likely initramfs-tools would not copy them to the initrd. Regards, Salvatore
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Control: tags -1 + confirmed On Tue, Dec 05, 2023 at 06:23:45AM +0100, Michael Ott wrote: > Package: src:linux > Version: 6.6.4-1~exp1 > Severity: important > > Dear Maintainer, > > After updating to the 6.6 kernel the password for my encryption does not > longer > work > > Please unlock disk nvme0n1p3_crypt: ** > device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT) > device-mapper: ioctl: error adding target to table > device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such file or > directory > cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or > options? > > Everything works with 6.5. I also downgrade systemd and cryptosetup but no > changes I suspect this is related to changes around https://git.kernel.org/linus/68cf01760bc0891074e813b9bb06d2696cac1c01 (but not verified, nor tracked down). Regards, Salvatore
Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work
Package: src:linux Version: 6.6.4-1~exp1 Severity: important Dear Maintainer, After updating to the 6.6 kernel the password for my encryption does not longer work Please unlock disk nvme0n1p3_crypt: ** device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT) device-mapper: ioctl: error adding target to table device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such file or directory cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or options? Everything works with 6.5. I also downgrade systemd and cryptosetup but no changes -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 20KF001GGE product_version: ThinkPad X280 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N20ET66W (1.51 ) board_vendor: LENOVO board_name: 20KF001GGE board_version: Not Defined ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08) Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [17aa:2256] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2256] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:2256] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [17aa:2256] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:2256] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) Subsystem: Lenovo Sunrise Point-LP Thermal subsystem [17aa:2256] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:2256] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1) (prog-if 00 [Normal decode]) Subsystem: Lenovo Sunrise Point-LP PCI Express Root Port [17aa:2256] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation
