On Fri, Apr 17, 2015 at 7:38 PM, Mike Snitzer <snit...@redhat.com> wrote: > On Fri, Apr 17 2015 at 4:11pm -0400, > Murilo Opsfelder Araújo <mopsfel...@gmail.com> wrote: > >> Hello, everyone. >> >> Right after I enter my passphrase to unlock my cryptsetup partition, >> it displays the following error and asks for cryptsetup password again >> (it got stuck on this loop). >> >> This issue was introduced in next-20150413. next-20150410 is working just >> fine. >> >> Any hint on how to debug this? >> >> Unlocking the disk /dev/disk/by-uuid/<uuid> (sda5_crypt) >> Enter passphrase: ***** >> [ 244.239821] device-mapper: table: 252:0: crypt: Error allocating crypto >> tfm >> device-mapper: reload ioctl on failed: No such file or directory >> Failed to open temporary keystore device. >> device-mapper: remove ioctl on temporary-cryptsetup-239 failed: No >> such device or address >> device-mapper: reload ioctl on temporary-cryptsetup-239 failed: No >> such device or address >> device-mapper: remove ioctl on temporary-cryptsetup-239 failed: No >> such device or address >> device-mapper: remove ioctl on temporary-cryptsetup-239 failed: No >> such device or address >> device-mapper: remove ioctl on temporary-cryptsetup-239 failed: No >> such device or address >> device-mapper: remove ioctl on temporary-cryptsetup-239 failed: No >> such device or address > > git diff next-20150410^..next-20150413 drivers/md/dm-crypt.c points to > this commit as the nly dm-crpt.c change: > https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=5977907937afa2b5584a874d44ba6c0f56aeaa9c > > Which appears unrelated given your "crypt: Error allocating crypto tfm" > error. > > But any chance you can try reverting that commit from next-20150413 and > re-test just to be absolutely sure?
Hello, Mike. I've reverted that commit from both next-20150413 and next-20150415. In both cases, I got the same error, no success. -- Murilo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
