From: Mike Snitzer <snitzer@redhat.com>
To: "Murilo Opsfelder Araújo" <mopsfelder@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: Device mapper failed to open temporary keystore device
Date: Fri, 17 Apr 2015 18:38:49 -0400 [thread overview]
Message-ID: <20150417223848.GD4028@redhat.com> (raw)
In-Reply-To: <CA+LKeY6Vm=hWj+gaKxm5JqLqehu8557OX2101a8roKas6WcsFg@mail.gmail.com>
On Fri, Apr 17 2015 at 4:11pm -0400,
Murilo Opsfelder Araújo <mopsfelder@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?
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(-)
next prev parent reply other threads:[~2015-04-17 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 20:11 Device mapper failed to open temporary keystore device Murilo Opsfelder Araújo
2015-04-17 22:38 ` Mike Snitzer [this message]
2015-04-18 2:00 ` Herbert Xu
2015-04-19 17:08 ` Murilo Opsfelder Araújo
2015-04-22 23:48 ` Murilo Opsfelder Araújo
2015-04-19 17:03 ` Murilo Opsfelder Araújo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150417223848.GD4028@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mopsfelder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox