From: Bart Van Assche <bvanassche@acm.org>
To: "Peter Wang (王信友)" <peter.wang@mediatek.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "vamshigajjela@google.com" <vamshigajjela@google.com>,
"alok.a.tiwari@oracle.com" <alok.a.tiwari@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"chenyuan0y@gmail.com" <chenyuan0y@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"ping.gao@samsung.com" <ping.gao@samsung.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v2 1/2] ufs: core: Introduce ufshcd_mcq_poll_n_cqe_lock()
Date: Thu, 14 May 2026 09:20:12 -0700 [thread overview]
Message-ID: <d7547792-62a7-409f-9906-c5f3854a0866@acm.org> (raw)
In-Reply-To: <23d57dd91882a3014c0d97a7b08b81117ade5b72.camel@mediatek.com>
On 5/14/26 12:34 AM, Peter Wang (王信友) wrote:
> However, the UFS ISR still cannot acquire
> the spinlock and executes an unknown task that disables IRQs,
> the duration of which is controlled by F2FS.
I see this as an F2FS bug. It is widely known that bi_end_io callbacks
may be called from interrupt context and hence should finish quickly.
Thanks,
Bart.
next prev parent reply other threads:[~2026-05-14 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 17:14 [PATCH v2 0/2] ufs-qcom: Reduce interrupt latency Bart Van Assche
2026-04-02 17:14 ` [PATCH v2 1/2] ufs: core: Introduce ufshcd_mcq_poll_n_cqe_lock() Bart Van Assche
2026-05-13 6:50 ` Peter Wang (王信友)
2026-05-13 19:26 ` Bart Van Assche
2026-05-14 7:34 ` Peter Wang (王信友)
2026-05-14 16:20 ` Bart Van Assche [this message]
2026-04-02 17:14 ` [PATCH v2 2/2] ufs: qcom: Reduce interrupt latency Bart Van Assche
2026-04-30 16:23 ` Martin K. Petersen
2026-04-30 16:21 ` [PATCH v2 0/2] ufs-qcom: " Martin K. Petersen
2026-04-30 17:21 ` Bart Van Assche
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=d7547792-62a7-409f-9906-c5f3854a0866@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alok.a.tiwari@oracle.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chenyuan0y@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=ping.gao@samsung.com \
--cc=vamshigajjela@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