Re: ext3 filesystem is not recognized after losetup -e aes

Dennison Williams wrote: > Here is the setup: MD software RAID 5 on 4 disks (md0), a LVM logical > volume (/dev/volume_group/logical_volume) comprised of one physical > device (/dev/md0), a encryption layer provided by the cryptoloop driver > (losetup -e aes /dev/loop0 /dev/volume_group/logical_vol

[RFC 2/2] [crypto] make the crypto subsystem fully modular

Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]> --- crypto/Kconfig |2 +- crypto/Makefile|3 ++- crypto/api.c |3 +++ include/linux/crypto.h |7 --- 4 files changed, 6 insertions(+), 9 deletions(-) diff --git a/crypto/Kconfig b/crypto/Kconfig ind

[RFC 1/2] [XFRM] remove ifdef crypto

and select the crypto subsystem if neccessary Signed-off-by: Sebastian Siewior <[EMAIL PROTECTED]> --- net/xfrm/Kconfig |1 + net/xfrm/xfrm_algo.c |2 -- 2 files changed, 1 insertions(+), 2 deletions(-) diff --git a/net/xfrm/Kconfig b/net/xfrm/Kconfig index 577a4f8..74ab643 100644 --

[RFC 0/2] make crypto fully modularly

Hello Herbert, I grep'ed for CONFIG_CRYPTO and crypto_has_alg() users and noticed that only xfrm_algo.c must be fixed (patch #1). The second patch than groups the four files together to a module. I didn't add MODULE_AUTHOR() because I did not know who it might be but I guess it would be you :) Se