linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Torsten Duwe <duwe@lst.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org
Subject: Re: af_alg broken in 3.12
Date: Fri, 3 Feb 2017 13:05:48 +0100	[thread overview]
Message-ID: <20170203120548.GA31291@lst.de> (raw)
In-Reply-To: <20170201121305.GA3260@lst.de>

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

  reply	other threads:[~2017-02-03 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 12:13 af_alg broken in 3.12 Torsten Duwe
2017-02-03 12:05 ` Torsten Duwe [this message]
2017-02-14 15:30   ` [PATCH] Fix af_alg " Torsten Duwe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170203120548.GA31291@lst.de \
    --to=duwe@lst.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).