linux-kernel - Re: Device mapper failed to open temporary keystore device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150417223848.GD4028@redhat.com>
Date:	Fri, 17 Apr 2015 18:38:49 -0400
From:	Mike Snitzer <snitzer@...hat.com>
To:	Murilo Opsfelder Araújo <mopsfelder@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alasdair Kergon <agk@...hat.com>, dm-devel@...hat.com,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: Device mapper failed to open temporary keystore device

On Fri, Apr 17 2015 at  4:11pm -0400,
Murilo Opsfelder Araújo <mopsfelder@...il.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?

There are also some crypto changes that could very easily be the cause
of your problem (cc'ing Herbert), e.g.:

$ git diff next-20150410^..next-20150413 -- crypto | diffstat
 algapi.c         |   13 ++++-
 algif_hash.c     |    4 -
 algif_skcipher.c |    4 -
 sha1_generic.c   |  102 ++++++++----------------------------------
 sha256_generic.c |  133 ++++++++-----------------------------------------------
 sha512_generic.c |  123 ++++++++------------------------------------------
 6 files changed, 76 insertions(+), 303 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/