From: "Thomas D." <whissi@whissi.de>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Sasha Levin <sasha.levin@oracle.com>,
Milan Broz <gmazyland@gmail.com>, Jiri Slaby <jslaby@suse.cz>,
Stephan Mueller <smueller@chronox.de>
Cc: Willy Tarreau <w@1wt.eu>,
"dvyukov@google.com" <dvyukov@google.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Ondrej Kozina <okozina@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: Broken userspace crypto in linux-4.1.18
Date: Wed, 24 Feb 2016 01:10:55 +0100 [thread overview]
Message-ID: <56CCF50F.5010803@whissi.de> (raw)
In-Reply-To: <CAA-+O6H8TQxrKOQAL+s+PGnkOJe-f3dEs-wKGbM1BFZ7_aC2dg@mail.gmail.com>
Hi,
I have applied Milan's patch on top of 4.1.18. I can reboot and open all
of my LUKS-encrypted disks. "cryptsetup benchmark" also works.
However, don't we need all the recent changes from
"crypto/algif_skcipher.c", too?
-Thomas
next prev parent reply other threads:[~2016-02-24 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56C47DF9.6030704@whissi.de>
[not found] ` <20160217233353.GC31125@1wt.eu>
[not found] ` <56C50725.6080408@whissi.de>
[not found] ` <4580306.arupsYiYbb@positron.chronox.de>
[not found] ` <56C591E7.5080808@suse.cz>
[not found] ` <56C5A66E.5010905@whissi.de>
[not found] ` <56C87929.8040304@whissi.de>
[not found] ` <56C9E865.3050500@gmail.com>
2016-02-23 21:02 ` [PATCH] Re: Broken userspace crypto in linux-4.1.18 Milan Broz
2016-02-23 21:21 ` Sasha Levin
[not found] ` <CAA-+O6H8TQxrKOQAL+s+PGnkOJe-f3dEs-wKGbM1BFZ7_aC2dg@mail.gmail.com>
2016-02-24 0:10 ` Thomas D. [this message]
2016-02-24 2:24 ` Greg KH
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=56CCF50F.5010803@whissi.de \
--to=whissi@whissi.de \
--cc=dvyukov@google.com \
--cc=gmazyland@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jslaby@suse.cz \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okozina@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=smueller@chronox.de \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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).