Andrew Morton wrote: > Fruhwirth Clemens wrote: >> >> If this bug is fixed, we can go ahead and add cryptoloop which is ready >> and tested. > > Does it use the crypto framework which is present in the 2.5 kernel? Yes. > If it does not then the cryptoloop implementation which you mention > is inappropriate for inclusion. > > If it does then it would be nice to see the full patchset. http://therapy.endorphin.org/patches/cryptoloop-0.2-2.5.58.diff It's basically a stub. The lock of the cipher_context can be removed since post-2.5.58 a new call has been added which makes the IV an argument. However, that's a minor change. In case you want to test it, you need to patch losetup too, since it needs to parse /proc/crypto. http://therapy.endorphin.org/patches/losetup-2.5.diff Regards, Clemens p.s.: Andrew please send me carbon copies of your mails. Thanks.