mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bean Huo <beanhuo@iokpp.de>
To: Stanley Jhu <stanleyjhu@google.com>,
	"Martin K . Petersen" <mkp@kernel.org>,
	 linux-scsi@vger.kernel.org
Cc: "James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
	 Bart Van Assche <bvanassche@acm.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Bean Huo <beanhuo@micron.com>,
	 Peter Wang <peter.wang@mediatek.com>,
	Can Guo <can.guo@oss.qualcomm.com>,
	linux-kernel@vger.kernel.org,  stable@vger.kernel.org
Subject: Re: [PATCH v2 0/4] scsi: ufs: core: Factor hba->outstanding_reqs helper and fix double completion
Date: Sun, 18 Oct 2026 21:52:31 +0200	[thread overview]
Message-ID: <2e042211ca0ebc974ad5ec4c0de9f3f93b3c75c0.camel@iokpp.de> (raw)
In-Reply-To: <20261017084403.875420-1-stanleyjhu@google.com>

On Sat, 2026-10-17 at 16:43 +0800, Stanley Jhu wrote:
> In Single Doorbell (SDB) mode, ufshcd_clear_lu_cmds() clears a transfer
> request slot in the controller and completes the request without
> claiming its bit in hba->outstanding_reqs. A subsequent ufshcd_poll()
> call sees the stale bit with its doorbell bit cleared and completes the
> request a second time, causing a double DMA unmap.
> 
> Patch 1 adds __ufshcd_clear_outstanding_reqs() and
> ufshcd_clear_outstanding_reqs() to share the bit-claim logic across
> ufshcd_poll() and ufshcd_abort() with no functional change. Patch 2 uses
> the new helper in ufshcd_clear_lu_cmds() to fix the SDB double
> completion. Patch 3 uses the new helper in ufshcd_eh_timed_out(). It is
> a follow-on cleanup and is not needed for the fix. Patch 4 removes a
> WARN_ONCE() whose condition is always false.
> 
> This series is based on mkp/for-next (db8b4d2bf2d3).
> 
> Tested on QEMU ARM64 UFS in SDB and MCQ modes across LU reset, polled
> and interrupt I/O, and task abort without double completion or DMA
> unmap warnings.
> 
> Changes since v1:
> - Add a helper for clearing hba->outstanding_reqs and use it in
>   ufshcd_poll(), ufshcd_abort(), and ufshcd_clear_lu_cmds()
>   (Bart Van Assche).
> - Convert ufshcd_eh_timed_out() to use the new helper in patch 3.
> - Remove an always-false WARN_ONCE() in patch 4.
> - Link to v1:
> https://lore.kernel.org/r/20261016085403.1711740-1-stanleyjhu@google.com
> 
> Stanley Jhu (4):
>   scsi: ufs: core: Add a helper for clearing hba->outstanding_reqs
>   scsi: ufs: core: Fix double completion in ufshcd_clear_lu_cmds()
>   scsi: ufs: core: Use ufshcd_clear_outstanding_reqs() in
>     ufshcd_eh_timed_out()
>   scsi: ufs: core: Remove an always-false WARN_ONCE()
> 

Hi Stanley,

For the whole series:

Reviewed-by: Bean Huo <beanhuo@micron.com>

One more place has the same problem. In ufshcd_abort(), the "cmd was completed,
but without a notifying intr" path completes the request but leaves its bit set
in hba->outstanding_reqs:

if (!hba->mcq_enabled && !(reg & (1 << tag))) {
	...
	 __ufshcd_transfer_req_compl(hba, 1UL << tag);
	...
}


could use the new helper in the same way as patch 2?


 if (ufshcd_clear_outstanding_reqs(hba, BIT(tag)))
	ufshcd_compl_one_cqe(hba, tag, NULL);

Kind regards,
Bean



  parent reply	other threads:[~2026-10-18 19:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17  8:43 Stanley Jhu
2026-10-17  8:44 ` [PATCH v2 1/4] scsi: ufs: core: Add a helper for clearing hba->outstanding_reqs Stanley Jhu
2026-10-19 20:50   ` Bart Van Assche
2026-10-17  8:44 ` [PATCH v2 2/4] scsi: ufs: core: Fix double completion in ufshcd_clear_lu_cmds() Stanley Jhu
2026-10-17  8:44 ` [PATCH v2 3/4] scsi: ufs: core: Use ufshcd_clear_outstanding_reqs() in ufshcd_eh_timed_out() Stanley Jhu
2026-10-17  8:44 ` [PATCH v2 4/4] scsi: ufs: core: Remove an always-false WARN_ONCE() Stanley Jhu
2026-10-19 20:45   ` Bart Van Assche
2026-10-18 19:52 ` Bean Huo [this message]
2026-10-19  4:29   ` [PATCH v2 0/4] scsi: ufs: core: Factor hba->outstanding_reqs helper and fix double completion Stanley Jhu
2026-10-19 20:43   ` Bart Van Assche
2026-10-20  3:16     ` Peter Wang
2026-10-19 10:47 ` Peter Wang
2026-10-20  3:15 Peter Wang (王信友)

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=2e042211ca0ebc974ad5ec4c0de9f3f93b3c75c0.camel@iokpp.de \
    --to=beanhuo@iokpp.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alim.akhtar@samsung.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=mkp@kernel.org \
    --cc=peter.wang@mediatek.com \
    --cc=stable@vger.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®