From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752712AbdBCMFx (ORCPT ); Fri, 3 Feb 2017 07:05:53 -0500 Received: from verein.lst.de ([213.95.11.211]:47761 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752531AbdBCMFu (ORCPT ); Fri, 3 Feb 2017 07:05:50 -0500 Date: Fri, 3 Feb 2017 13:05:48 +0100 From: Torsten Duwe To: Jiri Slaby Cc: stable@vger.kernel.org, Herbert Xu , linux-kernel@vger.kernel.org Subject: Re: af_alg broken in 3.12 Message-ID: <20170203120548.GA31291@lst.de> References: <20170201121305.GA3260@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170201121305.GA3260@lst.de> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 01, 2017 at 01:13:05PM +0100, Torsten Duwe wrote: > Hi Herbert, > > you sent a backport of 6de62f15b581f920ade22d758f4c338311c2f0d4 to be included > in the 3.12 branch (as b2a0707817d3dec83652bb460a7775613058ae), but this leaves > af_alg broken for unkeyed hash functions: [...] > Mainline has meanwhile seen many fixes to this change; can you suggest an elegant > and crisp backport for these as well? > If Herbert does not have a better idea, I suggest to back out this change and fix dynamically allocated key structures for the individual algorithms instead, for the older branches. Any other suggestions? Torsten