From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Thu, 24 Jul 2014 22:20:54 +0200 (CEST) Received: by mail-we0-f182.google.com with SMTP id k48so3356344wev.27 for ; Thu, 24 Jul 2014 13:20:54 -0700 (PDT) Message-ID: <53D16AA3.9070401@gmail.com> Date: Thu, 24 Jul 2014 22:20:51 +0200 From: Milan Broz MIME-Version: 1.0 References: <53CEE763.4030409@archlinux.org> <53CF681B.8030500@gmail.com> In-Reply-To: <53CF681B.8030500@gmail.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] libcryptsetup kernel feature detection fails on boot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?windows-1252?Q?Thomas_B=E4chler?= , dm-crypt@saout.de On 07/23/2014 09:45 AM, Milan Broz wrote: > On 23.7.2014 0:36, Thomas B=E4chler 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. >=20 > Hm, yes, that's possible... dmcrypt is now needed only on activation > (previaously it was loaded earlier perhaps). >=20 > 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