From: Bart Van Assche <bvanassche@acm.org>
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>,
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 v3 2/7] scsi: ufs: core: Add a helper for clearing hba->outstanding_reqs
Date: Tue, 20 Oct 2026 09:58:18 -0700 [thread overview]
Message-ID: <e6305f92-dbdc-4f3c-8702-4611014167b6@acm.org> (raw)
In-Reply-To: <20261020082110.3511797-3-stanleyjhu@google.com>
On 10/20/26 1:21 AM, Stanley Jhu wrote:
> +static unsigned long __ufshcd_clear_outstanding_reqs(struct ufs_hba *hba,
> + unsigned long mask,
> + bool from_irq)
> + __must_hold(&hba->outstanding_lock)
> +{
> + unsigned long completed_reqs = mask & hba->outstanding_reqs;
> +
> + if (from_irq) {
> + /* Do not complete polled requests from interrupt context. */
> + ufshcd_clear_polled(hba, &completed_reqs);
> + }
> + hba->outstanding_reqs &= ~completed_reqs;
> +
> + return completed_reqs;
> +}
> +
> +static unsigned long ufshcd_clear_outstanding_reqs(struct ufs_hba *hba,
> + unsigned long mask)
> +{
> + guard(spinlock_irqsave)(&hba->outstanding_lock);
> + return __ufshcd_clear_outstanding_reqs(hba, mask, false);
> +}
Please add a short comment above the above two functions that explains
the meaning of the return value.
> /*
> * Return: > 0 if one or more commands have been completed or 0 if no
> * requests have been completed.
> @@ -6071,12 +6094,9 @@ static int ufshcd_poll(struct Scsi_Host *shost, unsigned int queue_num)
>
> spin_lock_irqsave(&hba->outstanding_lock, flags);
> tr_doorbell = ufshcd_readl(hba, REG_UTP_TRANSFER_REQ_DOOR_BELL);
> - completed_reqs = ~tr_doorbell & hba->outstanding_reqs;
> - if (queue_num == UFSHCD_POLL_FROM_INTERRUPT_CONTEXT) {
> - /* Do not complete polled requests from interrupt context. */
> - ufshcd_clear_polled(hba, &completed_reqs);
> - }
> - hba->outstanding_reqs &= ~completed_reqs;
> + completed_reqs =
> + __ufshcd_clear_outstanding_reqs(hba, ~tr_doorbell,
> + queue_num == UFSHCD_POLL_FROM_INTERRUPT_CONTEXT);
The above line is about 98 columns wide. That's too much - all other
code in this driver is 80 columns wide. One way to address this is by
introducing a local "from_irq" boolean variable:
+ from_irq = queue_num == UFSHCD_POLL_FROM_INTERRUPT_CONTEXT;
+ completed_reqs = __ufshcd_clear_outstanding_reqs(hba, ~tr_doorbell,
+ from_irq);
Otherwise this patch looks good to me.
Bart.
next prev parent reply other threads:[~2026-10-20 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 8:21 [PATCH v3 0/7] scsi: ufs: core: Factor hba->outstanding_reqs helper and fix double completions Stanley Jhu
2026-10-20 8:21 ` [PATCH v3 1/7] scsi: ufs: core: Remove an always-false WARN_ONCE() Stanley Jhu
2026-10-20 16:53 ` Bart Van Assche
2026-10-20 8:21 ` [PATCH v3 2/7] scsi: ufs: core: Add a helper for clearing hba->outstanding_reqs Stanley Jhu
2026-10-20 16:58 ` Bart Van Assche [this message]
2026-10-20 8:21 ` [PATCH v3 3/7] scsi: ufs: core: Fix double completion in ufshcd_clear_lu_cmds() Stanley Jhu
2026-10-20 8:21 ` [PATCH v3 4/7] scsi: ufs: core: Use ufshcd_clear_outstanding_reqs() in ufshcd_eh_timed_out() Stanley Jhu
2026-10-20 8:21 ` [PATCH v3 5/7] scsi: ufs: core: Fix double release " Stanley Jhu
2026-10-20 17:11 ` Bart Van Assche
2026-10-20 8:21 ` [PATCH v3 6/7] scsi: ufs: core: Fix double release in ufshcd_abort() Stanley Jhu
2026-10-20 8:21 ` [PATCH v3 7/7] scsi: ufs: core: Do not release a reserved request " 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=e6305f92-dbdc-4f3c-8702-4611014167b6@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=beanhuo@micron.com \
--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®