[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Questions about loop-aes and the implementation of encryptedfilesystems
Lars Bungum wrote:
> On Thu, 2004-02-26 at 19:37, Jari Ruusu wrote:
> > Device backed (partition backed) loops are ok with journaling file systems
> > at least when used with loop-AES. Mainline (current -bk version)
> > loop+cryptoloop combo is no longer journaling file system safe.
>
> I'm glad to hear it's safe as such file systems is a desire here. But I
> would like to know also why this is the case. I suppose what I really
> fail to understand is why this isn't safe in the cryptoloop system.
> Maybe there is somewhere I can read up on this?
Mainline (current -bk version) loop no longer guarantees write ordering.
Journal commits may reach disk before file system modifications reach disk.
IOW, it is no longer crash proof.
loop-AES has always supported correct write ordering with device backed
loops, and will continue to do so.
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/