[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240912151038.GA5858@lst.de>
Date: Thu, 12 Sep 2024 17:10:38 +0200
From: Christoph Hellwig <hch@....de>
To: John Garry <john.g.garry@...cle.com>
Cc: Christoph Hellwig <hch@....de>, axboe@...nel.dk, song@...nel.org,
yukuai3@...wei.com, kbusch@...nel.org, sagi@...mberg.me,
James.Bottomley@...senPartnership.com, martin.petersen@...cle.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, linux-nvme@...ts.infradead.org,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH RFC 4/4] md/raid0: Atomic write support
On Thu, Sep 12, 2024 at 03:48:09PM +0100, John Garry wrote:
>
> I actually now think that I should change bio_split() to return NULL for
> splitting a REQ_ATOMIC, like what do for ZONE_APPEND - calling bio_split()
> like this is a common pattern in md RAID personalities. However, none of
> the md RAID code check for a NULL split, which they really should, so I can
> make that change also.
bio_split is a bit of a mess - even NULL isn't very good at returning
what caused it to fail. Maybe a switch to ERR_PTR and an audit of
all callers might be a good idea.
Powered by blists - more mailing lists