Control: found -1 2:2.1.0-5+deb10u2 On Tue, 12 Oct 2021 at 00:33:32 +0200, Guilhem Moulin wrote: > On Mon, 11 Oct 2021 at 22:09:07 +0200, Marc Lehmann wrote: >> Specifically, the machine didn't have enough ram, probably because the >> default algorithm (argon) requires more ram than the machine had. > > Could you please share the memory cost of the PBKDF, and also the output > of `free` just before running cryptsetup? That would help us trying to > reproduce this and forward the issue upstream. I tried to reproduce > this but only managed to trigger the OOM killer. > > Also did you run luksFormat on that same machine (and didn't remove > memory sticks afterwards)?
I was actually able to reproduce this with buster's 2.1.0, but doing the
same thing after upgrading to bullseye or sid yields
(initramfs) cryptsetup luksOpen /dev/vda5 test_crypt
Enter passphrase for /dev/vda5:
[ 5.236310] device-mapper: uevent: version 1.0.3
[ 5.240230] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised:
dm-de...@redhat.com
Not enough available memory to open a keyslot.
which sounds alright. Did you run reportbug(1) from the affected system
or from an older one?
Looking at the upstream git log, I found
206b70c837f29c8b34cb0d80ae496870550ec50c
which fixes https://gitlab.com/cryptsetup/cryptsetup/-/issues/488 which looks
really familiar :-)
--
Guilhem.
signature.asc
Description: PGP signature
