From: Greg KH <gregkh@linuxfoundation.org>
To: Zhaoyang Li <lizy04@hust.edu.cn>
Cc: stable@vger.kernel.org, dzm91@hust.edu.cn,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Dhruva Gole" <d-gole@ti.com>, "Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH 6.1.y] spi: cadence-qspi: fix pointer reference in runtime PM hooks
Date: Sun, 21 Dec 2025 17:31:40 +0100 [thread overview]
Message-ID: <2025122106-value-precook-634a@gregkh> (raw)
In-Reply-To: <20250516062528.420927-1-lizy04@hust.edu.cn>
On Fri, May 16, 2025 at 02:25:28PM +0800, Zhaoyang Li wrote:
> From: Théo Lebrun <theo.lebrun@bootlin.com>
>
> [ Upstream commit 32ce3bb57b6b402de2aec1012511e7ac4e7449dc ]
>
> dev_get_drvdata() gets used to acquire the pointer to cqspi and the SPI
> controller. Neither embed the other; this lead to memory corruption.
>
> On a given platform (Mobileye EyeQ5) the memory corruption is hidden
> inside cqspi->f_pdata. Also, this uninitialised memory is used as a
> mutex (ctlr->bus_lock_mutex) by spi_controller_suspend().
>
> Fixes: 2087e85bb66e ("spi: cadence-quadspi: fix suspend-resume implementations")
> Reviewed-by: Dhruva Gole <d-gole@ti.com>
> Signed-off-by: Théo Lebrun <theo.lebrun@bootlin.com>
> Link: https://msgid.link/r/20240222-cdns-qspi-pm-fix-v4-1-6b6af8bcbf59@bootlin.com
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Zhaoyang Li <lizy04@hust.edu.cn>
> ---
> drivers/spi/spi-cadence-quadspi.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Turns out you used a LLM tool to generate this backport. Any specific
reason why you didn't identify that and tell us you did so?
thanks,
greg k-h
next prev parent reply other threads:[~2025-12-21 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 6:25 [PATCH 6.1.y] spi: cadence-qspi: fix pointer reference in runtime PM hooks Zhaoyang Li
2025-05-16 18:26 ` Sasha Levin
2025-12-21 16:31 ` Greg KH [this message]
2025-12-22 3:29 ` Zhaoyang Li
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=2025122106-value-precook-634a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=d-gole@ti.com \
--cc=dzm91@hust.edu.cn \
--cc=lizy04@hust.edu.cn \
--cc=stable@vger.kernel.org \
--cc=theo.lebrun@bootlin.com \
/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.