From: "J. Paul Reed" <preed@sigkill.com>
To: stable@vger.kernel.org
Subject: Fixing userspace crypto in 3.14.x?
Date: Sat, 12 Mar 2016 16:26:54 -0800 [thread overview]
Message-ID: <20160313002654.GA3563@sigkill.com> (raw)
Userspace crypto has been broken in the 3.14 series since 3.14.61; see:
http://marc.info/?t=145571848500001&r=1&w=2
Specifically:
http://marc.info/?l=linux-crypto-vger&m=145597880120294&w=2
and
http://marc.info/?l=linux-crypto-vger&m=145579378307060&w=2
I waited a few 3.14 maintenance releases to see if this would get fixed,
but as of 3.14.64, it remains broken.
Are there any plans plans to fix this? (For those of us with luks-encrypted
partitions, the 3.14 tree is now unusable past 3.14.60.)
thanks,
preed
--
J. Paul Reed PGP: 0xDF8708F8 -- http://www.soberbuildengineer.com
=========================================================================
I've never seen an airplane yet that can read the type ratings on your
pilot's license. -- Chuck Boedecker
next reply other threads:[~2016-03-13 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 0:26 J. Paul Reed [this message]
2016-03-13 0:45 ` Fixing userspace crypto in 3.14.x? Greg KH
2016-03-13 1:10 ` J. Paul Reed
2016-03-13 3:02 ` Greg KH
2016-03-13 3:55 ` J. Paul Reed
2016-03-13 5:39 ` Greg KH
2016-03-13 9:05 ` J. Paul Reed
2016-03-24 2:31 ` J. Paul Reed
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=20160313002654.GA3563@sigkill.com \
--to=preed@sigkill.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).