On Fri, Jul 21, 2000 at 07:52:41PM +0200, Walter Hofmann wrote:
> I'm running 2.2.17pre12 with crypto patch 16.4.
>
> It seems that the decrypted data from a loop device is cached between
> destroys and new setups of loop devices. You cannot see this if you just
> mount the loop devices because mount seems unaffected, but fsck will
> show the error.
[snip]
Actually the bug is the opposite :) ...
> frodo:/home/wh # /usr/local/bin/losetup -e serpent /dev/loop0 /usr/local/loop/wh
> Password : correct password
> frodo:/home/wh # /sbin/e2fsck /dev/loop0
> e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> Group descriptors look bad... trying backup blocks...
> /sbin/e2fsck: Bad magic number in super-block while trying to open /dev/loop0
> frodo:/home/wh # mount /dev/loop0 /mnt
> frodo:/home/wh # umount /mnt
> frodo:/home/wh # /sbin/e2fsck /dev/loop0
> e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> /dev/loop0: clean, 4650/81920 files, 66139/163840 blocks
Since you have already set up the loop device with the right password, the
first fsck shouldn't fail. And since umount doesn't automagically losetup
-d /dev/loop0, it should not invalidate it's settings (password in this
case)
-- ____/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B \ o.O| 2F0D27DE025BE2302C =(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822 U chaos and madness await thee at its end." hkp://keys.pgp.comHandle via comment channels only.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:31 EST