From: Andi Kleen
Date: Wed Feb 18 2004 - 05:44:21 EST
Andrew Morton <akpm@xxxxxxxx> writes:
> - Added the dm-crypt driver: a crypto layer for device-mapper.
> People need to test and use this please. There is documentation at
> We should get this tested and merged up. We can then remove the nasty
> bio remapping code from the loop driver. This will remove the current
> ordering guarantees which the loop driver provides for journalled
> filesystems. ie: ext3 on cryptoloop will no longer be crash-proof.
> After that we should remove cryptoloop altogether.
> It's a bit late but cyptoloop hasn't been there for long anyway and it
> doesn't even work right with highmem systems (that part is fixed in -mm).
Is it guaranteed that this thing will be disk format compatible to cryptoloop?
(mainly in IVs and crypto algorithms)
While 2.3 and 2.4 have broken the on disk format of crypto loop several
times (each time to a new "improved and ultimately perfect format")
I don't think that's acceptable for a mature OS anymore.
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/