* Randy Dunlap | 2009-08-27 12:34:01 [-0700]: >> On 27/08/2009 Randy Dunlap wrote: >> > On Tue, 25 Aug 2009 19:58:52 -0400 Celejar wrote: >> > >> > > I'm having a pretty bizarre problem with my kernel crypto >> > > configuration. I need support for a bog standard LUKS (aes / >> > > cbc-essiv:sha256) / cryptsetup installation, but even after I enable >> > > virtually everything in the crypto section of the kernel configs, cbc >> > > fails to load. All the relevant modules are exist (dm-mod, dm-crypt, >> > > crypto_blkcipher, crypto_algapi, crypto_hash, aes_generic, >> > > sha256_generic), but even after modprobing / insmoding >> > > everything, /proc/crypto shows that aes and sha is there, but not cbc. >> > > >> > > The problem has been reproduced (using my kernel config) by Jonas >> > > Meurer, the Debian cryptsetup maintainer, so it's not just me ;). >> > > We've tried numerous different kernel versions in the .30 / .31 range. >> > > >> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541835 >> > > >> > > Does this mean that something else somewhere in the kernel needs to be >> > > configured but isn't, and the necessary dependency isn't properly >> > > declared? >> > > >> > > My config is at: >> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=45;filename=config-2.6.31-rc6-lizzie-00042-gb2add73;att=1;bug=541835 >> > > >> > > [I'm not subscribed to lkml; please cc me on responses] >> the problem rather is that loading the cbc blockcipher module simply >> does nothing. the module is listed in /proc/modules, but the blockcipher >> is still missing from /proc/crypto. Yes. cbc(aes) is auto-generated once someone requests such a cipher. The block modes are not listed. >> 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. >--- >~Randy Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
