From: Greg KH <gregkh@linuxfoundation.org>
To: bin.lan.cn@eng.windriver.com
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.6] crypto: starfive - Do not free stack buffer
Date: Tue, 3 Dec 2024 09:23:08 +0100 [thread overview]
Message-ID: <2024120340-vessel-pelican-1721@gregkh> (raw)
In-Reply-To: <20241203065213.67046-1-bin.lan.cn@eng.windriver.com>
On Tue, Dec 03, 2024 at 02:52:13PM +0800, bin.lan.cn@eng.windriver.com wrote:
> From: Jia Jie Ho <jiajie.ho@starfivetech.com>
>
> [ Upstream commit d7f01649f4eaf1878472d3d3f480ae1e50d98f6c ]
>
> RSA text data uses variable length buffer allocated in software stack.
> Calling kfree on it causes undefined behaviour in subsequent operations.
>
> Cc: <stable@vger.kernel.org> #6.7+
The cc: says 6.7 and newer, and yet you are wanting this for 6.6.y?
Why? Why ignore what the author asked for?
thanks,
greg k-h
next prev parent reply other threads:[~2024-12-03 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 6:52 [PATCH 6.6] crypto: starfive - Do not free stack buffer bin.lan.cn
2024-12-03 8:23 ` Greg KH [this message]
2024-12-03 8:34 ` Bin Lan
2024-12-03 8:48 ` Greg KH
2024-12-03 18:13 ` Sasha Levin
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=2024120340-vessel-pelican-1721@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bin.lan.cn@eng.windriver.com \
--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