From: Damien Le Moal <dlemoal@kernel.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org
Cc: Wilfred Mallawa <wilfred.mallawa@wdc.com>
Subject: Re: [PATCH blktests v2 2/2] zbd/002: do not check write pointers of conventional zones
Date: Thu, 26 Feb 2026 13:18:19 +0900 [thread overview]
Message-ID: <94a65175-ea75-4597-a504-1915a746f506@kernel.org> (raw)
In-Reply-To: <20260220132351.273758-3-shinichiro.kawasaki@wdc.com>
On 2/20/26 22:23, Shin'ichiro Kawasaki wrote:
> After the recent change in util-linux [1], the 'blkzone report' command
> no longer reports numeric values for write pointers when the write
> pointers are invalid. Instead, now it reports the sting 'N/A'. The test
> case zbd/002 assumed that 'blkzone report' command would return valid
> write pointer values for conventional zones. The test case worked before
> the blkzone change, but now the test fails because of the wrong
> assumption.
>
> To avoid the failure, do not check write pointer values when the zone
> type is conventional.
>
> Link: [1] https://github.com/util-linux/util-linux/commit/b032247f48d8b6a13bf8541eb663c779e448f568
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Looks good to me.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-02-26 4:18 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 [this message]
2026-02-27 6:48 ` [PATCH blktests v2 0/2] zbd: adjust to recent blkzone change Shinichiro Kawasaki
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=94a65175-ea75-4597-a504-1915a746f506@kernel.org \
--to=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--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