On 02/23/2011 09:18 PM, Lukas Czerner wrote: >>> Now, there might be some way around this to allow trimming encrypted >>> volumes without serious security issue, but this is rather question for >>> dm-crypt guys. >> >> Maybe making work the "discard" mount option ? There were discussion about TRIM on dm-crypt mailing list several times. one of it is here http://thread.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/4075/ ) Currently TRIM/discard is not intentionally supported on dm-crypt. Security aspects are obvious (leaking of used blocks at least). The decision cannot be done in kernel automatically, you can have different policies, in some situation TRIM of encryption device is not problem, in other it can be disaster. So plan is to implement TRIM in dm-crypt but never enable it by default. You will be able to enable it per-device using device-mapper message with explicit user request. (we are using the same message mechanism for wiping/resuming key when freezing device). In future this can be flag for LUKS2 metadata but current version of LUKS doesn't allow such extensions. Milan -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
