From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tao Cui <cui.tao@linux.dev>,
linux-next@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Damien Le Moal <dlemoal@kernel.org>,
linux-block@vger.kernel.org, cuitao@kylinos.cn
Subject: Re: next-20260917 and next-20260918: merge of the block tree breaks all zoned devices
Date: Sun, 20 Sep 2026 17:18:27 +0200 [thread overview]
Message-ID: <aq_5QycDLgQGCc86@sirena.org.uk> (raw)
In-Reply-To: <20260920231226.771a0e21@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-20 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 12:58 next-20260917 and next-20260918: merge of the block tree breaks all zoned devices Tao Cui
2026-09-20 13:12 ` Stephen Rothwell
2026-09-20 15:18 ` Mark Brown [this message]
2026-09-20 22:37 ` Damien Le Moal
2026-09-21 0:49 ` Tao Cui
2026-09-21 2:07 ` Damien Le Moal
2026-09-21 2:31 ` Damien Le Moal
2026-09-21 10:29 ` Mark Brown
2026-09-21 8:24 ` Mark Brown
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=aq_5QycDLgQGCc86@sirena.org.uk \
--to=broonie@kernel.org \
--cc=axboe@kernel.dk \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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