From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: herbert@gondor.apana.org.au, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] crypto: pcrypt - Fix user-after-free on module unload" failed to apply to 4.19-stable tree
Date: Sun, 2 Feb 2020 17:34:32 -0500 [thread overview]
Message-ID: <20200202223432.GE1732@sasha-vm> (raw)
In-Reply-To: <1580395207158126@kroah.com>
On Thu, Jan 30, 2020 at 03:40:07PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-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 07bfd9bdf568a38d9440c607b72342036011f727 Mon Sep 17 00:00:00 2001
>From: Herbert Xu <herbert@gondor.apana.org.au>
>Date: Tue, 19 Nov 2019 17:41:31 +0800
>Subject: [PATCH] crypto: pcrypt - Fix user-after-free on module unload
>
>On module unload of pcrypt we must unregister the crypto algorithms
>first and then tear down the padata structure. As otherwise the
>crypto algorithms are still alive and can be used while the padata
>structure is being freed.
>
>Fixes: 5068c7a883d1 ("crypto: pcrypt - Add pcrypt crypto...")
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Conflicts due to 63d3578892dc ("crypto: pcrypt - remove padata cpumask
notifier"), cleaned up and queued for all trees.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-02 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 14:40 FAILED: patch "[PATCH] crypto: pcrypt - Fix user-after-free on module unload" failed to apply to 4.19-stable tree gregkh
2020-02-02 22:34 ` 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=20200202223432.GE1732@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.