From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: Re: [PATCH blktests v2 0/2] zbd: adjust to recent blkzone change
Date: Fri, 27 Feb 2026 06:48:00 +0000 [thread overview]
Message-ID: <aaE9xHGzie-Pim6y@shinmob> (raw)
In-Reply-To: <20260220132351.273758-1-shinichiro.kawasaki@wdc.com>
On Feb 20, 2026 / 22:23, Shin'ichiro Kawasaki wrote:
> After the recent change in util-linux [1], 'blkzone report' command no
> longer reports numeric values for write pointers when the write pointers
> are invalid. This change caused two failure symptoms in the zbd test
> group. The first failure symptom is arithmetic failures by evaluating
> the string 'N/A' as a numeric value. The second failure symptom is
> write pointer validity check failure for conventional zones. The two
> patches in this series address the two failure symptoms respectively.
>
> Link: [1] https://github.com/util-linux/util-linux/commit/b032247f48d8b6a13bf8541eb663c779e448f568
FYI, I applied the patches. Of note is that I made a slight change to the
block comment in the first patch when I applied it.
prev parent reply other threads:[~2026-02-27 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 13:23 [PATCH blktests v2 0/2] zbd: adjust to recent blkzone change Shin'ichiro Kawasaki
2026-02-20 13:23 ` [PATCH blktests v2 1/2] zbd/rc: do not use invalid write pointer values by blkzone report Shin'ichiro Kawasaki
2026-02-26 4:17 ` Damien Le Moal
2026-02-20 13:23 ` [PATCH blktests v2 2/2] zbd/002: do not check write pointers of conventional zones Shin'ichiro Kawasaki
2026-02-26 4:18 ` Damien Le Moal
2026-02-27 6:48 ` Shinichiro Kawasaki [this message]
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=aaE9xHGzie-Pim6y@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=wilfred.mallawa@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