From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "bvanassche@acm.org" <bvanassche@acm.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "beanhuo@micron.com" <beanhuo@micron.com>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"avri.altman@sandisk.com" <avri.altman@sandisk.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"nitin.rawat@oss.qualcomm.com" <nitin.rawat@oss.qualcomm.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH] ufs: core: Fix an error handler crash
Date: Fri, 5 Dec 2025 08:31:14 +0000 [thread overview]
Message-ID: <14cf8cdad876f68d59cf487ae16ce561458c403e.camel@mediatek.com> (raw)
In-Reply-To: <20251204170457.994851-1-bvanassche@acm.org>
On Thu, 2025-12-04 at 07:04 -1000, Bart Van Assche wrote:
> The UFS error handler may be activated before SCSI scanning has
> started and
> hence before hba->ufs_device_wlun has been set. Check the
> hba->ufs_device_wlun pointer before using it.
>
> Cc: Peter Wang <peter.wang@mediatek.com>
> Cc: Nitin Rawat <nitin.rawat@oss.qualcomm.com>
> Fixes: e23ef4f22db3 ("scsi: ufs: core: Fix error handler host_sem
> issue")
> Fixes: f966e02ae521 ("scsi: ufs: core: Fix runtime suspend error
> deadlock")
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Thanks for fix this bug.
Reviewed-by: Peter Wang <peter.wang@mediatek.com>
next prev parent reply other threads:[~2025-12-05 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 17:04 [PATCH] ufs: core: Fix an error handler crash Bart Van Assche
2025-12-04 17:38 ` Nitin Rawat
2025-12-04 18:26 ` Bart Van Assche
2025-12-05 8:31 ` Peter Wang (王信友) [this message]
2025-12-06 15:06 ` Nitin Rawat
2025-12-09 2:58 ` Martin K. Petersen
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=14cf8cdad876f68d59cf487ae16ce561458c403e.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=adrian.hunter@intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@sandisk.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=quic_nguyenb@quicinc.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