From: Peter Wang <peter.wang@mediatek.com>
To: Bart Van Assche <bvanassche@acm.org>,
Stanley Jhu <stanleyjhu@google.com>
Cc: "Martin K. Petersen" <mkp@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@sandisk.com>,
Bean Huo <beanhuo@micron.com>, Can Guo <can.guo@oss.qualcomm.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] scsi: ufs: core: Release command resources instead of force-completing
Date: Tue, 22 Sep 2026 11:03:25 +0800 [thread overview]
Message-ID: <6288ff21af758e0f3739edb6c33abe3bfbdba3dd.camel@mediatek.com> (raw)
In-Reply-To: <16af6539-24f8-425e-b411-f191897acfce@acm.org>
On Mon, 2026-09-21 at 09:51 -0700, Bart Van Assche wrote:
> > Agreed for the path where SCSI EH drove the reset. The case I am
> > unsure
> > about is the other caller: ufshcd_err_handler() also runs from
> > hba->eh_work, scheduled by ufshcd_check_errors() on UIC and
> > controller
> > errors. Those commands have not timed out and are not on
> > shost->eh_cmd_q, so SCSI EH never finishes them, and the handler
> > leaves
> > them to the reset path on purpose:
> >
> > /*
> > * if host reset is required then skip clearing the pending
> > * transfers forcefully because they will get cleared during
> > * host reset and restore
> > */
> >
> > Should those simply wait for the block layer timeout and come back
> > through SCSI EH?
>
> That sounds good to me.
>
> Thanks,
>
> Bart.
Hi Bart,
It appears unreasonable to wait for the entire 30 second timeout,
as many UIC errors recover promptly. The resulting 30 second stall
would manifest as a noticeable UI freeze. Maybe we shouldn’t let
eh_host_reset_handler call the EH handler at all?
Thanks
Peter
next prev parent reply other threads:[~2026-09-22 3:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 14:33 [PATCH 0/2] scsi: ufs: core: Fix SCSI EH command ownership and remove force_compl Stanley Jhu
2026-09-20 14:33 ` [PATCH 1/2] scsi: ufs: core: Release command resources instead of force-completing Stanley Jhu
2026-09-21 0:41 ` Bart Van Assche
2026-09-21 4:37 ` Stanley Jhu
2026-09-21 16:51 ` Bart Van Assche
2026-09-22 3:03 ` Peter Wang [this message]
2026-09-22 16:34 ` Bart Van Assche
2026-09-20 14:33 ` [PATCH 2/2] scsi: ufs: core: Remove unused force_compl parameter and MCQ helper Stanley Jhu
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=6288ff21af758e0f3739edb6c33abe3bfbdba3dd.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@sandisk.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=can.guo@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mkp@kernel.org \
--cc=stanleyjhu@google.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
all inboxes | Powered by JetHome®