From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>, <avri.altman@sandisk.com>,
<alim.akhtar@samsung.com>, <jejb@linux.ibm.com>,
<peter.wang@mediatek.com>, <wsd_upstream@mediatek.com>,
<linux-mediatek@lists.infradead.org>, <chun-hung.wu@mediatek.com>,
<alice.chao@mediatek.com>, <cc.chou@mediatek.com>,
<chaotian.jing@mediatek.com>, <tun-yu.yu@mediatek.com>,
<eddie.huang@mediatek.com>, <naomi.chu@mediatek.com>,
<ed.tsai@mediatek.com>
Subject: Re: [PATCH v1] ufs: core: Fix possible NULL pointer dereference in ufshcd_add_command_trace()
Date: Sat, 28 Feb 2026 17:37:26 -0500 [thread overview]
Message-ID: <yq1seak33dp.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <b680084c-88b1-4854-981b-316311452e56@acm.org> (Bart Van Assche's message of "Wed, 25 Feb 2026 11:45:29 -0800")
Hi Bart!
> Do you agree that the following should be added to this patch?
>
> Fixes: 4a52338bf288 ("scsi: ufs: core: Add trace event for MCQ")
If I hadn't already applied the patch I would add the tag. However, with
"Fix" and "NULL pointer dereference" in the title, hopefully some AI
will pick it up.
Worst case we can Cc: stable once Linus has pulled it...
--
Martin K. Petersen
prev parent reply other threads:[~2026-02-28 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 6:56 [PATCH v1] ufs: core: Fix possible NULL pointer dereference in ufshcd_add_command_trace() peter.wang
2026-02-23 17:13 ` Bart Van Assche
2026-02-24 5:29 ` Peter Wang (王信友)
2026-02-24 16:48 ` Bart Van Assche
2026-02-25 5:53 ` Peter Wang (王信友)
2026-02-24 16:50 ` Bart Van Assche
2026-02-25 2:08 ` Martin K. Petersen
2026-02-25 19:45 ` Bart Van Assche
2026-02-28 22:37 ` Martin K. Petersen [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=yq1seak33dp.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@sandisk.com \
--cc=bvanassche@acm.org \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=ed.tsai@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=naomi.chu@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=tun-yu.yu@mediatek.com \
--cc=wsd_upstream@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox