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

[Jari Ruusu]

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

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

http://mail.nl.linux.org/linux-crypto/2004-02/msg00006.html

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/