Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Anand Jain <anajain.sg@gmail.com>
To: fstests@vger.kernel.org, zlang@redhat.com, Zorro Lang <zlang@kernel.org>
Cc: linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-xfs@vger.kernel.org, linux-f2fs@vger.kernel.org,
	amir73il@gmail.com, hch@infradead.org,
	Anand Jain <asj@kernel.org>
Subject: Re: [PATCH v5 09/10] fstests: add pre_clone_tune_uuid() healper
Date: Thu, 21 May 2026 21:10:36 +0800	[thread overview]
Message-ID: <fbc03a78-0a6c-4c3a-9608-656d0df83d29@gmail.com> (raw)
In-Reply-To: <0d9f455d20145103faaf4e45262ee44418cbaca1.1779367627.git.asj@kernel.org>



On 21/5/26 20:54, Anand Jain wrote:
> pre_clone_tune_uuid() changes the UUID of the golden filesystem before it
> is cloned.
> 
> Signed-off-by: Anand Jain <asj@kernel.org>
> ---
>  common/rc | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/common/rc b/common/rc
> index 7ae9877918c8..1b3a32d9ea9b 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -1517,6 +1517,26 @@ _scratch_resvblks()
>  	esac
>  }
>  
> +pre_clone_tune_uuid()


I missed the "_" prefix for pre_clone_tune_uuid() to match
the common/rc style.

Zorro,

If there are no other rerolls, can you please fix it at merge
or should I resend?

Thanks


> +{
> +	local temp_mnt=$TEST_DIR/${seq}_mnt
> +	local dev=$1
> +
> +	case $FSTYP in
> +	xfs)
> +		_require_command "$XFS_ADMIN_PROG" "xfs_admin"
> +		$XFS_ADMIN_PROG -U generate $dev >> $seqres.full
> +		;;
> +	btrfs)
> +		_require_command "$BTRFS_TUNE_PROG" "btrfstune"
> +		$BTRFS_TUNE_PROG -m $dev
> +		;;
> +	*)
> +		_notrun "Require filesystem with metadata_uuid feature"
> +		;;
> +	esac
> +}
> +
>  _loop_image_create_clone()
>  {
>  	local -n _ret=$1


  reply	other threads:[~2026-05-21 13:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 12:54 [PATCH v5 0/10] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-05-21 12:54 ` [PATCH v5 01/10] fstests: add _loop_image_create_clone() helper Anand Jain
2026-05-21 12:54 ` [PATCH v5 02/10] fstests: add _clone_mount_option() helper Anand Jain
2026-05-21 12:54 ` [PATCH v5 03/10] fstests: add test for inotify isolation on cloned devices Anand Jain
2026-05-21 12:54 ` [PATCH v5 04/10] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-05-21 12:54 ` [PATCH v5 05/10] fstests: verify f_fsid for " Anand Jain
2026-05-21 12:54 ` [PATCH v5 06/10] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-05-21 12:54 ` [PATCH v5 07/10] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-05-21 12:54 ` [PATCH v5 08/10] fstests: verify exportfs file handles " Anand Jain
2026-05-21 12:54 ` [PATCH v5 09/10] fstests: add pre_clone_tune_uuid() healper Anand Jain
2026-05-21 13:10   ` Anand Jain [this message]
2026-05-21 12:55 ` [PATCH v5 10/10] fstests: test UUID consistency for clones with metadata_uuid Anand Jain

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=fbc03a78-0a6c-4c3a-9608-656d0df83d29@gmail.com \
    --to=anajain.sg@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=asj@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@kernel.org \
    --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