[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aK1ocfvjLrIR_Xf2@infradead.org>
Date: Tue, 26 Aug 2025 00:55:29 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: Christoph Hellwig <hch@...radead.org>, colyli@...nel.org, hare@...e.de,
tieren@...as.com, axboe@...nel.dk, tj@...nel.org,
josef@...icpanda.com, song@...nel.org, akpm@...ux-foundation.org,
neil@...wn.name, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
linux-raid@...r.kernel.org, yi.zhang@...wei.com,
yangerkun@...wei.com, johnny.chenyi@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>,
John Garry <john.g.garry@...cle.com>
Subject: Re: [PATCH RFC 4/7] md/raid10: convert read/write to use
bio_submit_split()
On Tue, Aug 26, 2025 at 09:13:41AM +0800, Yu Kuai wrote:
> > The NULL return should only happen for REQ_NOWAIT here, so maybe
> > give R10BIO_Returned a more descriptive name? Also please document
> > the flag in the header.
>
> And also atomic write here, if bio has to split due to badblocks here.
> The flag is refer to raid1. I can add cocument for both raid1 and raid10
> in this case.
Umm, that's actually a red flag. If a device guarantees atomic behavior
it can't just fail it. So I think REQ_ATOMIC should be disallowed
for md raid with bad block tracking.
>
Powered by blists - more mailing lists