From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Sun, 21 Feb 2016 08:14:01 +0100 (CET) Received: by mail-wm0-x229.google.com with SMTP id a4so122482564wme.1 for ; Sat, 20 Feb 2016 23:14:01 -0800 (PST) References: From: Milan Broz Message-ID: <56C963A8.4010009@gmail.com> Date: Sun, 21 Feb 2016 08:13:44 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Crypto-changes in some kernels List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Strauss , dm-crypt@saout.de On 02/20/2016 11:35 PM, Michael Strauss wrote: > Hi all, > > some (longterm stable) kernel got patches who seem to make them incompatible > with cryptsetup. See for details: > > http://thread.gmane.org/gmane.linux.kernel.stable/165742 > > I tried the git version of cryptsetup and that seem to fix it at least for > 4.1.18. I noticed no problems so far. > > A new tarball release would be a good idea I think. They have release proper stable kernel with backported compatible patches (it is kernel that changed API). I spent a lot of time testing when this happened mainline (there is link to discussion somewhere in the thread)... Yes, it is "fixed" (changed so it works even with new kernel API changes) in cryptsetup git and will be part of 1.7.1 release. But I will not hurry with releasing something now just because stable kernel maintainers are backporting things without any testing. (Anyway, 1.7.1 will be released this week.) Milan