From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH] Re: Broken userspace crypto in linux-4.1.18 To: Milan Broz , "Thomas D." , Jiri Slaby , Stephan Mueller References: <56C47DF9.6030704@whissi.de> <20160217233353.GC31125@1wt.eu> <56C50725.6080408@whissi.de> <4580306.arupsYiYbb@positron.chronox.de> <56C591E7.5080808@suse.cz> <56C5A66E.5010905@whissi.de> <56C87929.8040304@whissi.de> <56C9E865.3050500@gmail.com> <56CCC8D3.8040001@gmail.com> Cc: Willy Tarreau , "herbert@gondor.apana.org.au" , "dvyukov@google.com" , "stable@vger.kernel.org" , "linux-crypto@vger.kernel.org" , Greg KH , Ondrej Kozina , Linux Kernel Mailing List From: Sasha Levin Message-ID: <56CCCD6D.3040506@oracle.com> Date: Tue, 23 Feb 2016 16:21:49 -0500 MIME-Version: 1.0 In-Reply-To: <56CCC8D3.8040001@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 02/23/2016 04:02 PM, Milan Broz wrote: > On 02/21/2016 05:40 PM, Milan Broz wrote: >> > On 02/20/2016 03:33 PM, Thomas D. wrote: >>> >> Hi, >>> >> >>> >> FYI: v3.10.97, v3.14.61 and 3.18.27 are also affected. >>> >> >>> >> v4.3.6 works. Looks like the patch set is only compatible with >=linux-4.3. >>> >> >>> >> v3.12.54 works because it doesn't contain the patch in question. >> > >> > Hi, >> > >> > indeed, because whoever backported this patchset skipped two patches >> > from series (because of skcipher interface file was introduced later). > Ping? > > I always thought that breaking userspace is not the way mainline kernel > operates and here we break even stable tree... > > Anyone planning to release new kernel version with properly backported patches? > There is already a lot of downstream distro bugs reported. Hi Milan, I'd really like to see an ack on your patch by one of the crypto/ maintainers before putting it into a -stable release. Thanks, Sasha