On 07/23/2014 09:45 AM, Milan Broz wrote: > On 23.7.2014 0:36, Thomas Bächler wrote: >> Since cryptsetup 1.6.5, libcryptsetup fails to detect the kernel's >> features on boot. In particular, whenever the dm-crypt module is not >> loaded before configuring a mapping with libcryptsetup, the >> allow_discards option is not used. > > Hm, yes, that's possible... dmcrypt is now needed only on activation > (previaously it was loaded earlier perhaps). > > Well, the workaround for now is probably to always load dmcrypt module, > I'll try to fix it soon. It is fixed in devel git now. Thanks. (The main problem with detection of features is that without device-mapper target module loaded there is no way to get the version. And using only kernel version is not enough, e.g. RHEL systems often backports features.) Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
