From: Milan Broz <gmazyland@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Eric Wheeler <linux-crypto@lists.ewheeler.net>
Cc: "Wang, Rui Y" <rui.y.wang@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jean Delvare <jdelvare@suse.de>,
linux-crypto@vger.kernel.org, stable@vger.kernel.org
Subject: Re: crypto regression in 4.1.18: Check that kernel supports aes-cbc-essiv:sha256 cipher
Date: Wed, 2 Mar 2016 18:49:27 +0100 [thread overview]
Message-ID: <56D727A7.8030800@gmail.com> (raw)
In-Reply-To: <20160301025853.GB17542@kroah.com>
On 03/01/2016 03:58 AM, Greg KH wrote:
> On Tue, Mar 01, 2016 at 01:32:05AM +0000, Eric Wheeler wrote:
>> Hello all,
>>
>> We updated from 4.1.17 to 4.1.18 (same .config) and now get the following
>> error when trying to open a LUKS volume. We've reverted to 4.1.17 and it
>> still works, so except that I'm not sure which commit caused the problem,
>> it is likely one of the recent commits:
>>
>> When we `cryptsetup luksOpen` the volume we get this:
>>
>> Check that kernel supports aes-cbc-essiv:sha256 cipher (check syslog for more info).
>>
>> Note that I do not see any dm-crypto commits so I don't think its a
>> dm-crypto issue.
>>
>> I'm happy to test, but can someone who knows the crypto stack suggest
>> which of these patches I should focus on for testing? These are the
>> commits in 4.1.18 that could be relevant:
>
> There are some pending crypto backports to resolve this that hopefully
> will show up in the next release, whenever Sasha gets to it.
Also there is already released cryptsetup 1.7.1 that works even with this kernel.
Milan
next prev parent reply other threads:[~2016-03-02 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 1:32 crypto regression in 4.1.18: Check that kernel supports aes-cbc-essiv:sha256 cipher Eric Wheeler
2016-03-01 2:58 ` Greg KH
2016-03-02 17:49 ` Milan Broz [this message]
2016-03-07 4:02 ` Eric Wheeler
2016-03-10 5:55 ` Eric Wheeler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D727A7.8030800@gmail.com \
--to=gmazyland@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jdelvare@suse.de \
--cc=linux-crypto@lists.ewheeler.net \
--cc=linux-crypto@vger.kernel.org \
--cc=rui.y.wang@intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).