From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com ([66.111.4.28]:55384 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932148AbcCMD4A (ORCPT ); Sat, 12 Mar 2016 22:56:00 -0500 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6E04520622 for ; Sat, 12 Mar 2016 22:55:59 -0500 (EST) Date: Sat, 12 Mar 2016 19:55:57 -0800 From: "J. Paul Reed" To: Greg KH Cc: stable@vger.kernel.org Subject: Re: Fixing userspace crypto in 3.14.x? Message-ID: <20160313035557.GA15530@sigkill.com> References: <20160313002654.GA3563@sigkill.com> <20160313004510.GA5820@kroah.com> <20160313011053.GA11370@sigkill.com> <20160313030246.GD11289@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160313030246.GD11289@kroah.com> Sender: stable-owner@vger.kernel.org List-ID: On 12 Mar 2016 at 19:02:46, Greg KH arranged the bits on my disk to say: > 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? I already did: http://marc.info/?l=linux-crypto-vger&m=145620828015563&w=2 The thread I pointed you to was what I was told by the crypto list: http://marc.info/?l=linux-crypto-vger&m=145620853015626&w=2 In that thread, the developer was also apparently made aware: http://www.spinics.net/lists/linux-crypto/msg17931.html I think bringing it up to the developer and the crypto mailing list again is unlikely to get this issue addressed, as they are both aware of it. later, 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