From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:56600 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932169AbcCMDrg (ORCPT ); Sat, 12 Mar 2016 22:47:36 -0500 Date: Sat, 12 Mar 2016 19:02:46 -0800 From: Greg KH To: "J. Paul Reed" Cc: stable@vger.kernel.org Subject: Re: Fixing userspace crypto in 3.14.x? Message-ID: <20160313030246.GD11289@kroah.com> References: <20160313002654.GA3563@sigkill.com> <20160313004510.GA5820@kroah.com> <20160313011053.GA11370@sigkill.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160313011053.GA11370@sigkill.com> Sender: stable-owner@vger.kernel.org List-ID: On Sat, Mar 12, 2016 at 05:10:53PM -0800, J. Paul Reed wrote: > > On 12 Mar 2016 at 16:45:10, Greg KH arranged the bits on my disk to say: > > > 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. > > The following message in that thread has assumed-bad commit (and the > associated bisect log): > > http://marc.info/?l=linux-crypto-vger&m=145575300630247&w=2 > > As for backports, I'm merely a lowly kernel user. I don't see how that breaks anything in userspace, can you please bring this up with the developers of that patch and the crypto mailing list? thanks, greg k-h