stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "J. Paul Reed" <preed@sigkill.com>
Cc: stable@vger.kernel.org
Subject: Re: Fixing userspace crypto in 3.14.x?
Date: Sat, 12 Mar 2016 16:45:10 -0800	[thread overview]
Message-ID: <20160313004510.GA5820@kroah.com> (raw)
In-Reply-To: <20160313002654.GA3563@sigkill.com>

On Sat, Mar 12, 2016 at 04:26:54PM -0800, J. Paul Reed wrote:
> 
> 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.)

So, what patch should I revert from 3.10.y and 3.14.y to "fix" this?  I
thought only 4.1.y was affected.  Or better yet, I asked for backports
to resolve this, if someone could come up with them, that would be even
better.

thanks,

greg k-h

  reply	other threads:[~2016-03-13  1:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-13  0:26 Fixing userspace crypto in 3.14.x? J. Paul Reed
2016-03-13  0:45 ` Greg KH [this message]
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=20160313004510.GA5820@kroah.com \
    --to=greg@kroah.com \
    --cc=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).