From: Christoph Hellwig <hch@infradead.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Christoph Hellwig <hch@infradead.org>,
axboe@kernel.dk, neil@brown.name, akpm@linux-foundation.org,
linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, colyli@kernel.org, xni@redhat.com,
yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com, tieren@fnnas.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] block: fix disordered IO in the case recursive split
Date: Mon, 25 Aug 2025 02:15:41 -0700 [thread overview]
Message-ID: <aKwpvfDLgeNaGjnF@infradead.org> (raw)
In-Reply-To: <510600c4-5ff3-a02e-de6d-020fad771425@huaweicloud.com>
On Mon, Aug 25, 2025 at 02:15:49PM +0800, Yu Kuai wrote:
> > be resubmitted to current->bio_list, hence this patch won't break this
> > case, right?
>
> And xfs_rw_bdev() is not under submit_bio() context, current->bio_list
> is still NULL, means xfs_rw_bdev() is submitting bio one by one in the
> right lba order, the bio recursive handling is not related in this case.
Yes, usually not - unless we somehow eventually get the loop device
out a separate workque context.
next prev parent reply other threads:[~2025-08-25 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 7:47 [PATCH] block: fix disordered IO in the case recursive split Yu Kuai
2025-08-21 8:06 ` Coly Li
2025-08-21 8:43 ` Christoph Hellwig
2025-08-21 8:56 ` Yu Kuai
2025-08-21 9:02 ` Christoph Hellwig
2025-08-21 9:33 ` Hannes Reinecke
2025-08-21 9:42 ` Yu Kuai
2025-08-21 9:37 ` Yu Kuai
2025-08-25 6:15 ` Yu Kuai
2025-08-25 9:15 ` Christoph Hellwig [this message]
2025-08-25 9:17 ` Christoph Hellwig
2025-08-25 9:49 ` Yu Kuai
2025-08-21 15:19 ` Bart Van Assche
2025-08-21 9:16 ` Coly Li
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=aKwpvfDLgeNaGjnF@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=colyli@kernel.org \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neil@brown.name \
--cc=tieren@fnnas.com \
--cc=xni@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.