Re: Oopsing cryptoapi (or loop device?) on 2.6.*

[Jan Rychter <jan@rychter.com>]

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

>>>>> "Jari" == Jari Ruusu <jariruusu@users.sourceforge.net> writes:
 Jari> Michal Kwolek wrote:
 >> I've got a reproducible oops when using cryptoloop on vanilla 2.6.0,
 >> 2.6.1 and 2.6.2 (2.4.* works fine).
 >>
 >> Way to reproduce: dd if=/dev/urandom of=crypto bs=1024
 >> count=some_size losetup -e some_cipher /dev/loop0 crypto
 >> #Any of those commands causes oops and hard lockup:
 >> cp /dev/loop0 /dev/null mkreiserfs /dev/loop0 mkfs.ext2 /dev/loop0
 >>
 >> Loop without cryptoapi works fine: dd if=/dev/urandom of=crypto
 >> bs=1024 count=some_size losetup /dev/loop0 crypto cp /dev/loop0
 >> /dev/null
 >> #ok, no oops

 Jari> Can you try again using loop-AES? loop-AES does not fall apart
 Jari> like the mainline implementation does. loop-AES is here:

FWIW, I've just tried loop-AES with 2.4.24, after using cryptoapi for a
number of years. My machine froze dead in the midst of copying 2.8GB of
data onto my file-backed reiserfs encrypted loopback mount.

Since the system didn't ever freeze on me before and since I've had zero
problems with cryptoapi, I attribute the freeze to loop-AES.

Yes, I know this isn't a good bugreport...

--J.

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]