Hello there,
I ran the command below on top of linux-next kernel with the tag next-20230929,
and observed dm-crypt setup failed.
$ sudo cryptsetup open --type=plain --key-file=/dev/zero /dev/nullb0 test
device-mapper: reload ioctl on test (253:0) failed: No such file or directory
Kernel reported an error related to crypto.
device-mapper: table: 253:0: crypt: Error allocating crypto tfm (-ENOENT)
device-mapper: ioctl: error adding target to table
The failure was observed with null_blk and SATA HDD. It looks independent of
block device type.
I bisected and found that the commit 31865c4c4db2 ("crypto: skcipher - Add
lskcipher") is the trigger. I reverted the commit from next-20230929 together
with other four dependent commits below, and observed the failure disappears.
705b52fef3c7 ("crypto: cbc - Convert from skcipher to lskcipher")
32a8dc4afcfb ("crypto: ecb - Convert from skcipher to lskcipher")
3dfe8786b11a ("crypto: testmgr - Add support for lskcipher algorithms")
8aee5d4ebd11 ("crypto: lskcipher - Add compatibility wrapper around ECB")
Is this a known issue?
