From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: herbert@gondor.apana.org.au, smueller@chronox.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] crypto: algif_skcipher - Cap recv SG list at ctx->used" failed to apply to 4.9-stable tree
Date: Tue, 23 Jun 2020 09:15:04 -0400 [thread overview]
Message-ID: <20200623131504.GW1931@sasha-vm> (raw)
In-Reply-To: <1592913287117111@kroah.com>
On Tue, Jun 23, 2020 at 01:54:47PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 7cf81954705b7e5b057f7dc39a7ded54422ab6e1 Mon Sep 17 00:00:00 2001
>From: Herbert Xu <herbert@gondor.apana.org.au>
>Date: Fri, 29 May 2020 14:54:43 +1000
>Subject: [PATCH] crypto: algif_skcipher - Cap recv SG list at ctx->used
>
>Somewhere along the line the cap on the SG list length for receive
>was lost. This patch restores it and removes the subsequent test
>which is now redundant.
>
>Fixes: 2d97591ef43d ("crypto: af_alg - consolidation of...")
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>Reviewed-by: Stephan Mueller <smueller@chronox.de>
>Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
We don't have 2d97591ef43d ("crypto: af_alg - consolidation of duplicate
code") in our 4.9 and 4.4 trees.
We do carry an "out of tree" backport that fixes an issue silently fixed
by 2d97591ef43d, but it does not introduce the issue that this patch
fixes.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-06-23 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 11:54 FAILED: patch "[PATCH] crypto: algif_skcipher - Cap recv SG list at ctx->used" failed to apply to 4.9-stable tree gregkh
2020-06-23 13:15 ` Sasha Levin [this message]
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=20200623131504.GW1931@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=smueller@chronox.de \
--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