From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:58775 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753691AbcCMBEm (ORCPT ); Sat, 12 Mar 2016 20:04:42 -0500 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 757E42027B for ; Sat, 12 Mar 2016 20:04:41 -0500 (EST) Date: Sat, 12 Mar 2016 16:45:10 -0800 From: Greg KH To: "J. Paul Reed" Cc: stable@vger.kernel.org Subject: Re: Fixing userspace crypto in 3.14.x? Message-ID: <20160313004510.GA5820@kroah.com> References: <20160313002654.GA3563@sigkill.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160313002654.GA3563@sigkill.com> Sender: stable-owner@vger.kernel.org List-ID: 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