On Mon, 04 Sep 2006 12:02:28 EDT, [email protected] said: > Sorry for not catching this one earlier.. Sometime between 2.6.18-rc4-mm2 > and -mm3, something crept into the git-cryptodev.patch that breaks mounting > encrypted disks. What I have in /etc/fstab: And of course, after I spend time doing a -mm bisect, the problem evaporates in -rc5-mm1. ;) > /dev/rootvg/crypto1 /crypto/mount_dir ext3 nodev,nosuid,noexec,noauto,noatime,nodiratime,user,loop,encryption=aes 1 0 > My personal guess as "most likely suspect" (only obvious hit on cryptoloop): Looks like a self-inflicted screw-up in the .config. The relevant diff of the 2 .config files (the -rc4-mm3 had a 'patch -R < git-cryptodev' so the new options aren't in that .config) -# Linux kernel version: 2.6.18-rc4-mm3 -# Wed Aug 30 10:00:30 2006 +# Linux kernel version: 2.6.18-rc5-mm1 +# Mon Sep 4 16:22:37 2006 .... +CONFIG_CRYPTO_ALGAPI=y +CONFIG_CRYPTO_BLKCIPHER=y +CONFIG_CRYPTO_HASH=y +CONFIG_CRYPTO_MANAGER=y Does 'CONFIG_CRYPTOLOOP' need a 'SELECT CRYPTO_MANAGER' (or one of the other symbols)?
Attachment:
pgpV1HngW7fGl.pgp
Description: PGP signature
- Follow-Ups:
- References:
- Prev by Date: Re: [PATCH][RFC] request_firmware examples and MODULE_FIRMWARE
- Next by Date: Re: [PATCH 2.6.18-rc4 1/5] ieee1394: sbp2: workaround for write protect bit of Initio firmware
- Previous by thread: 2.6.18-rc4-mm3 crypto issues with encrypted disks
- Next by thread: Re: 2.6.18-rc4-mm3 crypto issues with encrypted disks
- Index(es):
 |