public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: Zorro Lang <zlang@redhat.com>, Christoph Hellwig <hch@lst.de>,
	Naohiro Aota <naohiro.aota@wdc.com>,
	linux-btrfs@vger.kernel.org,
	Hans Holmberg <hans.holmberg@wdc.com>,
	fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
	Carlos Maiolino <cem@kernel.org>
Subject: Re: [PATCH v5 2/3] common/zoned: add helpers for creation and teardown of zloop devices
Date: Thu, 16 Oct 2025 08:48:34 -0700	[thread overview]
Message-ID: <20251016154834.GN2591640@frogsfrogsfrogs> (raw)
In-Reply-To: <20251016152032.654284-3-johannes.thumshirn@wdc.com>

On Thu, Oct 16, 2025 at 05:20:31PM +0200, Johannes Thumshirn wrote:
> Add _create_zloop, _destroy_zloop and _find_next_zloop helper functions
> for creating destroying and finding the next free zloop device.
> 
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> ---
>  common/zoned | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 52 insertions(+)
> 
> diff --git a/common/zoned b/common/zoned
> index 41697b08..313e755e 100644
> --- a/common/zoned
> +++ b/common/zoned
> @@ -45,3 +45,55 @@ _require_zloop()
>  	    _notrun "This test requires zoned loopback device support"
>      fi
>  }
> +
> +_find_next_zloop()
> +{
> +    id=0
> +
> +    while true; do
> +        if [[ ! -b "/dev/zloop$id" ]]; then
> +            break
> +        fi
> +        id=$((id + 1))
> +    done
> +
> +    echo "$id"
> +}
> +
> +# Create a zloop device
> +# usage: _create_zloop <base_dir> <zone_size> <nr_conv_zones>
> +_create_zloop()
> +{
> +    local id="$(_find_next_zloop)"
> +
> +    if [ -n "$1" ]; then
> +        local zloop_base="$1"
> +    else
> +	local zloop_base="/var/local/zloop"

Inconsistent indenting (tab here, everywhere else in this function uses
four spaces)

> +    fi
> +
> +    if [ -n "$2" ]; then
> +        local zone_size=",zone_size_mb=$2"
> +    fi
> +
> +    if [ -n "$3" ]; then
> +        local conv_zones=",conv_zones=$3"
> +    fi
> +
> +    mkdir -p "$zloop_base/$id"
> +
> +    local zloop_args="add id=$id,base_dir=$zloop_base$zone_size$conv_zones"
> +
> +    echo "$zloop_args" > /dev/zloop-control
> +
> +    echo "/dev/zloop$id"

Same question as last time: shouldn't we only echo this if the
zloop-control write succeeds?

--D

> +}
> +
> +_destroy_zloop() {
> +	local zloop="$1"
> +
> +	test -b "$zloop" || return
> +	local id=$(echo $zloop | grep -oE '[0-9]+$')
> +
> +	echo "remove id=$id" > /dev/zloop-control
> +}
> -- 
> 2.51.0
> 
> 

  reply	other threads:[~2025-10-16 15:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 15:20 [PATCH v5 0/3] fstests: basic smoke test on zoned loop device Johannes Thumshirn
2025-10-16 15:20 ` [PATCH v5 1/3] common/zoned: add _require_zloop Johannes Thumshirn
2025-10-16 23:49   ` Naohiro Aota
2025-10-16 15:20 ` [PATCH v5 2/3] common/zoned: add helpers for creation and teardown of zloop devices Johannes Thumshirn
2025-10-16 15:48   ` Darrick J. Wong [this message]
2025-10-16 15:50     ` Johannes Thumshirn
2025-10-17  0:44       ` Naohiro Aota
2025-10-17 16:35         ` Darrick J. Wong
2025-10-17 18:38   ` Zorro Lang
2025-10-16 15:20 ` [PATCH v5 3/3] generic: basic smoke for filesystems on zoned block devices Johannes Thumshirn
2025-10-16 15:49   ` Darrick J. Wong
2025-10-16 23:48   ` Naohiro Aota
2025-10-16 23:54   ` Anand Jain
2025-10-17  4:17   ` Christoph Hellwig
2025-10-17 18:56   ` Zorro Lang
2025-10-18 11:13     ` Johannes Thumshirn
2025-10-18 14:05       ` Zorro Lang
2025-10-20  6:21         ` Johannes Thumshirn
2025-10-21  9:33           ` Johannes Thumshirn
2025-10-21 14:49             ` Darrick J. Wong
2025-10-22  4:32               ` hch
2025-10-22  7:24               ` Zorro Lang
2025-10-22  7:34                 ` hch
2025-10-22  4:35             ` hch
2025-10-22  6:27               ` Johannes Thumshirn
2025-10-22  6:33                 ` hch
2025-10-20  7:28     ` Christoph Hellwig

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=20251016154834.GN2591640@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=hch@lst.de \
    --cc=johannes.thumshirn@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=naohiro.aota@wdc.com \
    --cc=zlang@redhat.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