From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: zlang@kernel.org, hans.holmberg@wdc.com,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] common: skip zoned devices in _require_populate_commands
Date: Mon, 12 May 2025 08:08:24 -0700 [thread overview]
Message-ID: <20250512150824.GD2701446@frogsfrogsfrogs> (raw)
In-Reply-To: <20250512131819.629435-1-hch@lst.de>
On Mon, May 12, 2025 at 03:18:19PM +0200, Christoph Hellwig wrote:
> mdrestore doesn't work on zoned device, so skip tests using to
> pre-populate a file system image.
>
> This was previously papered over by requiring fallocate, which got
> removed in commit eff1baf42a79 ("common/populate: drop fallocate
> mode 0 requirement").
>
> Note that the populate helpers for placement on the data device anyway,
> so they never exercised the rt device. Maybe we should skip them for
> all rt device setups and not just zoned ones to save some execution
> time?
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> common/populate | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/common/populate b/common/populate
> index 50dc75d35259..6190eac7ad83 100644
> --- a/common/populate
> +++ b/common/populate
> @@ -20,6 +20,10 @@ _require_populate_commands() {
> _require_command "$XFS_DB_PROG" "xfs_db"
> _require_command "$WIPEFS_PROG" "wipefs"
> _require_command "$XFS_MDRESTORE_PROG" "xfs_mdrestore"
> +
> + # mdrestore can't restore to zoned devices
> + _require_non_zoned_device $SCRATCH_DEV
> + _require_non_zoned_device $SCRATCH_RTDEV
Do you need to _notrun the other mdrestore tests too?
I was wondering why this patch didn't add a helper:
# Check if mdrestore is supported, must come after _scratch_check
_require_scratch_mdrestore() {
_require_command "$XFS_MDRESTORE_PROG" "xfs_mdrestore"
_require_non_zoned_device $SCRATCH_DEV
[ "$USE_EXTERNAL" = yes -a ! -z "$SCRATCH_LOGDEV" ] && \
_require_non_zoned_device $SCRATCH_LOGDEV
[ "$USE_EXTERNAL" = yes -a ! -z "$SCRATCH_RTDEV" ] && \
_require_non_zoned_device $SCRATCH_RTDEV
}
which is then pasted in everywhere?
--D
> ;;
> ext*)
> _require_command "$DUMPE2FS_PROG" "dumpe2fs"
> --
> 2.47.2
>
>
next prev parent reply other threads:[~2025-05-12 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:18 [PATCH] common: skip zoned devices in _require_populate_commands Christoph Hellwig
2025-05-12 15:08 ` Darrick J. Wong [this message]
2025-05-12 15:27 ` 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=20250512150824.GD2701446@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.