From: Niklas Cassel <cassel@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Damien Le Moal <dlemoal@kernel.org>,
linux-block@vger.kernel.org, Niklas Cassel <cassel@kernel.org>
Subject: [PATCH 0/2] null_blk: zone resource management fixes
Date: Wed, 21 Oct 2026 22:21:01 +0200 [thread overview]
Message-ID: <20261021202100.2017938-4-cassel@kernel.org> (raw)
Patch 1 fixes writing, opening and finishing a closed zone when both the
open and the active zone limits are reached: null_blk fails the request
instead of closing an implicitly open zone, as ZBC-3 and NVMe ZNS
require.
Patch 2 fixes zone_readonly and zone_offline, which can close an
unrelated zone, or leak the closed zone count.
Both issues were reproduced, and the fixes tested, in QEMU, with
null_blk devices created through configfs (memory_backed=0 and 1,
CONFIG_PROVE_LOCKING=y).
Developed with the help of an AI coding assistant.
Niklas Cassel (2):
null_blk: fix opening closed zones at the active zone limit
null_blk: don't finish zones to set them read-only or offline
drivers/block/null_blk/zoned.c | 48 ++++++++++++++++++++++++++--------
1 file changed, 37 insertions(+), 11 deletions(-)
base-commit: f47d223627f80cb7a1eb14c585fe6cb35de5e984
--
2.56.0
next reply other threads:[~2026-10-21 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 20:21 Niklas Cassel [this message]
2026-10-21 20:21 ` [PATCH 1/2] null_blk: fix opening closed zones at the active zone limit Niklas Cassel
2026-10-22 7:09 ` Damien Le Moal
2026-10-21 20:21 ` [PATCH 2/2] null_blk: don't finish zones to set them read-only or offline Niklas Cassel
2026-10-22 7:15 ` Damien Le Moal
2026-10-22 7:36 ` Niklas Cassel
2026-10-22 7:42 ` Damien Le Moal
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=20261021202100.2017938-4-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox