public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"hch@infradead.org" <hch@infradead.org>
Cc: Sean Anderson <seanga2@gmail.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests] zbd/005: Limit block size to zone length
Date: Fri, 25 Apr 2025 11:37:28 +0900	[thread overview]
Message-ID: <9d14a000-49fe-4cc6-9720-9894d1b3fade@kernel.org> (raw)
In-Reply-To: <jzrhzy3qdj7tt2tlmoayo7pi367etl3furcbk3yvuh4zru2q7q@ikekotau7jvl>

On 4/24/25 20:30, Shinichiro Kawasaki wrote:
> On Apr 24, 2025 / 01:09, Christoph Hellwig wrote:
>> On Wed, Apr 23, 2025 at 12:49:57PM -0400, Sean Anderson wrote:
>>> The block size must be smaller than the zone length, otherwise fio will
>>> fail immediately.
>>
>> In theory yes.  In practice such a zone size makes zero sense, and will
>> not work with any zoned file systems or other users.
>>
>> So instead we should just warn about a silly zone size here instead
>> of trying to handle it.
> 
> As a similar idea, how about to skip the test case if the test target device's
> zone size is too small?
> 
> Sean, could you try out the patch below? It will skip the test case for your
> device, and you will not see the test case failing.
> 
> diff --git a/tests/zbd/005 b/tests/zbd/005
> index 4aa1ab5..d23eabe 100755
> --- a/tests/zbd/005
> +++ b/tests/zbd/005
> @@ -36,6 +36,13 @@ test_device() {
>  	_get_blkzone_report "${TEST_DEV}" || return $?
>  
>  	zone_idx=$(_find_first_sequential_zone) || return $?
> +
> +	# Ensure the zone size is large enough for the fio command below
> +	if ((ZONE_LENGTHS[zone_idx] < 512)); then
> +		SKIP_REASONS+=("too small zone size")

Nit: "zone size too small" would be better.

> +		return
> +	fi
> +
>  	offset=$((ZONE_STARTS[zone_idx] * 512))
>  	moaz=$(_test_dev_max_open_active_zones)
>  
> 
> 


-- 
Damien Le Moal
Western Digital Research

      parent reply	other threads:[~2025-04-25  2:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 16:49 [PATCH blktests] zbd/005: Limit block size to zone length Sean Anderson
2025-04-24  8:09 ` Christoph Hellwig
2025-04-24 11:30   ` Shinichiro Kawasaki
2025-04-24 13:56     ` Sean Anderson
2025-04-24 14:06       ` hch
2025-04-24 14:20         ` Sean Anderson
2025-04-24 14:23           ` hch
2025-04-25  4:04             ` Sean Anderson
2025-04-25 13:47               ` hch
2025-04-26  5:23                 ` Sean Anderson
2025-04-27  3:23                   ` Keith Busch
2025-04-25  2:37     ` Damien Le Moal [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=9d14a000-49fe-4cc6-9720-9894d1b3fade@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=seanga2@gmail.com \
    --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