From: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
To: Slavin Liu <bolin.liu@seu.edu.cn>, ogabbay@kernel.org
Cc: carl.vanderlip@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] accel/qaic: tolerate absent crashdump state during cleanup
Date: Fri, 2 Oct 2026 11:15:36 -0600 [thread overview]
Message-ID: <656b3e9e-4668-4369-8bde-d17bda52bd2f@oss.qualcomm.com> (raw)
In-Reply-To: <20260913125201.109964-1-bolin.liu@seu.edu.cn>
On 9/13/2026 6:52 AM, Slavin Liu wrote:
> A negative response can be sent before crashdump state is assigned.
> If queuing that response fails, cleanup receives NULL. Treat that as
> no owned crashdump resources instead of dereferencing it.
Please describe the exact sequence of functions which triggers this
scenario. I don't see it.
The change clearly protects against the ssr_crash parameter being NULL,
but that doesn't occur in relation to queuing responses.
> Detected by static analysis and reviewed with AI-assisted source auditing.
>
> Fixes: 6bc1fe6c748c ("accel/qaic: Collect crashdump from SSR channel")
> Assisted-by: LLM
> Signed-off-by: Slavin Liu <bolin.liu@seu.edu.cn>
> ---
> drivers/accel/qaic/qaic_ssr.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/accel/qaic/qaic_ssr.c b/drivers/accel/qaic/qaic_ssr.c
> index a98928654959..d9ba1d333cdb 100644
> --- a/drivers/accel/qaic/qaic_ssr.c
> +++ b/drivers/accel/qaic/qaic_ssr.c
> @@ -194,7 +194,11 @@ struct dump_file_meta {
>
> static void free_ssr_dump_info(struct ssr_crashdump *ssr_crash)
> {
> - struct ssr_dump_info *dump_info = ssr_crash->dump_info;
> + struct ssr_dump_info *dump_info;
> +
> + if (!ssr_crash)
> + return;
> + dump_info = ssr_crash->dump_info;
>
> ssr_crash->dump_info = NULL;
> if (!dump_info)
prev parent reply other threads:[~2026-10-02 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 12:52 Slavin Liu
2026-10-02 17:15 ` Jeff Hugo [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=656b3e9e-4668-4369-8bde-d17bda52bd2f@oss.qualcomm.com \
--to=jeff.hugo@oss.qualcomm.com \
--cc=bolin.liu@seu.edu.cn \
--cc=carl.vanderlip@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@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
all inboxes | Powered by JetHome®