On Sun, Sep 20, 2026 at 11:12:26PM +1000, Stephen Rothwell wrote:
> On Sun, 20 Sep 2026 20:58:34 +0800 Tao Cui <cui.tao@linux.dev> wrote:

> I no longer run linux-next, please email Mark Brown (cc'd).

> [The rest kept for Mark's benefit]

Thanks.

> > I ran into this while testing a blk-iocost series of mine (charging
> > zone appends as writes) against a zoned null_blk: the device simply
> > does not show up, whether configured through module parameters or
> > configfs.  null_blk prints "using native zone append" and then
> > add_disk() fails silently with -ENODEV.

> > Taking the axboe side of the function makes nullb0 come back on
> > next-20260918 here (host-managed, chunk_sectors 131072), so it looks
> > like the merge should just have taken that side.

> > Same conflict, same bad outcome twice in a row now, so tomorrow's
> > merge may hit it again unless the block tree has moved on in this
> > area.

I did say when I did that merge that I had no confidence in it but
nobody responded.  Can you please send me a commit on top of current
-next which fixes up the resolution appropriately?  I can drop extra
fixups in relatively easily, it's probably safer to take something that
you have tested.