From: Celejar <celejar@gmail.com>
To: Sebastian Andrzej Siewior <sebastian@ml.breakpoint.cc>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Jonas Meurer <jonas@freesources.org>,
541835@bugs.debian.org, lkml <linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org
Subject: Bug#541835: [pkg-cryptsetup-devel] Bug#541835: crypto configuration / dependencies broken
Date: Sun, 30 Aug 2009 20:06:56 -0400 [thread overview]
Message-ID: <20090830200656.dbd56f89.celejar@gmail.com> (raw)
In-Reply-To: <20090830153722.GA28497@Chamillionaire.breakpoint.cc>
On Sun, 30 Aug 2009 17:37:22 +0200
Sebastian Andrzej Siewior <sebastian@ml.breakpoint.cc> wrote:
> * Sebastian Andrzej Siewior | 2009-08-28 10:00:56 [+0200]:
>
> >>> the problem is not reproducible with a debian/unstable 2.6.30.6 kernel,
> >>> even though it has cbc compiled as module as well. but if I recompile
> >>> the same kernel sources with Celejars kernel .config, the problem
> >>> occurs. thus it must be related to the kernel config in some way.
> >It must be the kernel confing since I run .30.stable and it works. I try
> >to look at it later.
>
> Your kernel config is fine, the problem is that the initramfs tools do
> not copy all of the required modules into the initramfs. The missing
> modles are:
> - cryptomgr: that one is responsible to load the cbc and aes module and
> bind them to cbc(aes)
> - chainiv: that one creates IVs if the "user" does not specify one.
> dm-crypt probably does not use that one but is required due to the way
> crypto works atm.
> - krng: provides random numbers and is required by chainiv.
>
> If you add those three to /etc/initramfs/modules than it should work.
Right your are! It now works, thanks very much. I guess the catch was
that the working (stock Debian) kernel config built cryptomgr
(CRYPTO_MANAGER and CRYPTO_MANAGER2) and krng (CRYPTO_RNG2, although
not CRYPTO_RNG) and chainiv (CRYPTO_BLKCIPHER2, although not
CRYPTO_BLKCIPHER - I have the impression that chainiv is now
controlled by the BLKCIPHER options?) into the kernel, not as modules,
so I wasn't hit by the initramfs failure until I built them as modules
(I have a bit of a fetish for building everything as a module,
especially when using initrd's :/).
> Could someone please look at initramfs to figure out why those three
> modules are not copied in this reduced setup?
Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
next prev parent reply other threads:[~2009-08-31 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090825195852.1dfacb6c.celejar@gmail.com>
[not found] ` <20090827095516.6817be1e.randy.dunlap@oracle.com>
[not found] ` <20090827183500.GC24973@resivo.wgnet.de>
2009-08-27 19:34 ` [pkg-cryptsetup-devel] Bug#541835: crypto configuration / dependencies broken Randy Dunlap
2009-08-28 8:00 ` Sebastian Andrzej Siewior
2009-08-30 15:37 ` Sebastian Andrzej Siewior
2009-08-31 0:06 ` Celejar [this message]
2009-08-31 15:52 ` Jonas Meurer
2009-08-31 21:16 ` Sebastian Andrzej Siewior
2009-09-01 0:51 ` Jonas Meurer
2009-09-01 21:11 ` Sebastian Andrzej Siewior
2009-09-03 3:22 ` Herbert Xu
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=20090830200656.dbd56f89.celejar@gmail.com \
--to=celejar@gmail.com \
--cc=541835@bugs.debian.org \
--cc=jonas@freesources.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sebastian@ml.breakpoint.cc \
/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;
as well as URLs for NNTP newsgroup(s).