LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Michael S. Tsirkin" <m.s.tsirkin@gmail.com>,
	Alasdair G Kergon <agk@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	dm-crypt@saout.de
Subject: Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping
Date: Wed, 20 Feb 2008 12:23:21 +0100	[thread overview]
Message-ID: <47BC0DA9.1030607@redhat.com> (raw)
In-Reply-To: <8f53421d0802192343v2267cb66ub579d4503e3b7eb1@mail.gmail.com>

Michael S. Tsirkin wrote:
> I am booting a thinkpad T60p off of an encrypted disk (with crypto
> modules in initramfs).
> This works fine in 2.6.24, but in both 2.6.25-rc1 and 2.6.25-rc2
> won't boot with the following messages on the console
> (copied by hand, sorry about typos):
>         device-mapper: table: 254:0:crypt
>         Error allocating crypto tfm
>         Failed to setup dm_crypt key mapping.
>         check kernel for support for the aes-cbc-essiv:sha256
>         cipher spec and verify that /dev/sda6 contains at least 133 sectors.
>         Failed to read from storage.
> 
> git bisec points to the following commit:
> 
>         commit 3a7f6c990ad04e6f576a159876c602d14d6f7fef
>         dm crypt: use async crypto
> 
> Reverting commit 3a7f6c990ad04e6f576a159876c602d14d6f7fef
> on top of 2.6.25-rc2 results in a bootable configuration for me.
> 
> .config attached.

It seems that some module dependency was lost, 
dm-crypt with async crypto depends now on crypto_blkcipher module
for this configuration.

Herbert, any following change required for dm-crypt or it is only
crypto subsystem issue?
(With old kernel/dm-crypt it loads "blkcipher" not "crypto_blkcipher",
maybe some initramdisk change required too...)

Milan
--
mbroz@redhat.com


       reply	other threads:[~2008-02-20 11:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8f53421d0802192343v2267cb66ub579d4503e3b7eb1@mail.gmail.com>
2008-02-20 11:23 ` Milan Broz [this message]
2008-02-20 17:24   ` Herbert Xu
2008-02-20 17:47     ` Milan Broz
2008-02-20 17:58       ` Herbert Xu
2008-02-20 20:29         ` Michael S. Tsirkin
2008-02-22 12:34         ` Herbert Xu
2008-02-25 19:03           ` Jan Niehusmann
2008-03-07 18:14           ` Dan Williams
2008-03-08  1:24             ` Herbert Xu
2008-03-08  3:42               ` Dan Williams
2008-03-08 12:28                 ` Herbert Xu
2008-03-07 18:18           ` Tony Luck

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=47BC0DA9.1030607@redhat.com \
    --to=mbroz@redhat.com \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dm-crypt@saout.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.s.tsirkin@gmail.com \
    --cc=rjw@sisk.pl \
    --subject='Re: 2.6.25-rc[1,2]: failed to setup dm-crypt key mapping' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).