From: Christoph Hellwig <hch@infradead.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: Christoph Hellwig <hch@infradead.org>,
jiucheng.xu@amlogic.com, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
jianxin.pan@amlogic.com, tuan.zhang@amlogic.com,
Gao Xiang <xiang@kernel.org>,
linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] block: avoild hang when bio_list is non-NULL in submit_bio_wait()
Date: Mon, 2 Mar 2026 06:29:40 -0800 [thread overview]
Message-ID: <aaWe1PsmzYatc_zR@infradead.org> (raw)
In-Reply-To: <dddf1754-d575-4f4b-a11c-09847d0d0475@linux.alibaba.com>
On Mon, Mar 02, 2026 at 10:23:04PM +0800, Gao Xiang wrote:
> > > I've trimmed down the call stack, as follows:
> > >
> > > f2fs_submit_read_io
> > > submit_bio
> > > mmc_blk_mq_recovery
> > > z_erofs_endio
> > > vm_map_ram
> >
> > ->bi_end_io code really should not be having random in_atomic()
> > checks that make it completely different, but even if they have
>
> Thanks for the head-up.
>
> For this part, I'm pretty sure we need this particular one
> otherwise the scheduling performance (latency sensitive)
> is unacceptable for all Android phone users.
Where do you regularly get user context calls to ->bi_end_io?
next prev parent reply other threads:[~2026-03-02 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 2:51 [PATCH] block: avoild hang when bio_list is non-NULL in submit_bio_wait() Jiucheng Xu via B4 Relay
2026-03-02 13:50 ` Christoph Hellwig
2026-03-02 14:23 ` Gao Xiang
2026-03-02 14:29 ` Christoph Hellwig [this message]
2026-03-02 14:31 ` Gao Xiang
2026-03-03 2:03 ` Jiucheng Xu
2026-03-03 2:11 ` Gao Xiang
2026-03-03 2:17 ` Jiucheng Xu
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=aaWe1PsmzYatc_zR@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=hsiangkao@linux.alibaba.com \
--cc=jianxin.pan@amlogic.com \
--cc=jiucheng.xu@amlogic.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tuan.zhang@amlogic.com \
--cc=xiang@kernel.org \
/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