Linux-f2fs-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Suveer Jain via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zorro Lang <zlang@kernel.org>
Cc: djwong@kernel.org, fstests@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v8 02/13] fstests: add _clone_mount_option() helper
Date: Tue, 1 Sep 2026 21:54:05 +0800	[thread overview]
Message-ID: <4226c2b6-d108-4666-9ac9-b52830b3fd50@kernel.org> (raw)
In-Reply-To: <apbGwZODzZIvOyi0@zlang-mailbox>

On 1/9/26 20:39, Zorro Lang wrote:
> On Sat, Jul 25, 2026 at 03:38:59PM +0800, Anand Jain wrote:
>> Adds _clone_mount_option() helper function to handle filesystem-specific
>> requirements for mounting cloned devices. Abstract the need for -o nouuid
>> on XFS.
>>
>> Signed-off-by: Anand Jain <asj@kernel.org>
>> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
>> ---
>>  common/rc | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
>>
>> diff --git a/common/rc b/common/rc
>> index e8ff5be0c547..53e5d9d43af6 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -414,6 +414,19 @@ _scratch_mount_options()
>>  					$SCRATCH_DEV $SCRATCH_MNT
>>  }
>>  
>> +# Return filesystem-specific mount options required for mounting clone/snapshot
>> +# devices.
>> +_clone_mount_option()
> 
> Just a minor nitpick :) For consistency with other *_mount_options functions
> (in common/rc), I suggest using "options" instead of "option" -- _clone_mount_options
> 

I'm okay with that, though this rename will impact the rest of the patch
series too.

Thanks, Anand


>> +{
>> +	case "$FSTYP" in
>> +	xfs)
>> +		# Allow mounting a duplicate filesystem on the same host
>> +		echo "-o nouuid"
>> +		;;
>> +	*)
>> +	esac
>> +}
>> +
>>  _supports_filetype()
>>  {
>>  	local dir=$1
>> -- 
>> 2.43.0
>>



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2026-09-01 13:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25  7:38 [f2fs-dev] [PATCH v8 0/13] fstests: add test coverage for cloned filesystem ids Anand Jain via Linux-f2fs-devel
2026-07-25  7:38 ` [f2fs-dev] [PATCH v8 01/13] fstests: add _loop_image_create_clone() helper Anand Jain via Linux-f2fs-devel
2026-09-01 12:33   ` Zorro Lang via Linux-f2fs-devel
2026-09-01 13:52     ` Anand Suveer Jain via Linux-f2fs-devel
2026-07-25  7:38 ` [f2fs-dev] [PATCH v8 02/13] fstests: add _clone_mount_option() helper Anand Jain via Linux-f2fs-devel
2026-09-01 12:39   ` Zorro Lang via Linux-f2fs-devel
2026-09-01 13:54     ` Anand Suveer Jain via Linux-f2fs-devel [this message]
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 03/13] fstests: add FSNOTIFYWAIT_PROG Anand Jain via Linux-f2fs-devel
2026-09-01 15:37   ` Zorro Lang via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 04/13] fstests: add _require_fanotify_function Anand Jain via Linux-f2fs-devel
2026-09-01 15:42   ` Zorro Lang via Linux-f2fs-devel
2026-09-01 22:39     ` Anand Suveer Jain via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 05/13] fstests: add _require_unique_f_fsid() helper Anand Jain via Linux-f2fs-devel
2026-09-01 16:09   ` Zorro Lang via Linux-f2fs-devel
2026-09-01 23:32     ` Anand Suveer Jain via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 06/13] fstests: add SEMANAGE_PROG Anand Jain via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 07/13] fstests: verify fanotify isolation on cloned filesystems Anand Jain via Linux-f2fs-devel
2026-09-01 18:23   ` Zorro Lang via Linux-f2fs-devel
2026-09-04  6:14     ` Anand Suveer Jain via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 08/13] fstests: verify f_fsid for " Anand Jain via Linux-f2fs-devel
2026-09-01 18:51   ` Zorro Lang via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 09/13] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain via Linux-f2fs-devel
2026-09-01 19:12   ` Zorro Lang via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 10/13] fstests: verify IMA isolation on cloned filesystems Anand Jain via Linux-f2fs-devel
2026-09-01 19:58   ` Zorro Lang via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 11/13] fstests: verify exportfs file handles " Anand Jain via Linux-f2fs-devel
2026-09-01 20:29   ` Zorro Lang via Linux-f2fs-devel
2026-09-01 20:30   ` Zorro Lang via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 12/13] fstests: add _change_metadata_uuid helper Anand Jain via Linux-f2fs-devel
2026-09-01 20:53   ` Zorro Lang via Linux-f2fs-devel
2026-07-25  7:39 ` [f2fs-dev] [PATCH v8 13/13] fstests: test UUID consistency for clones with metadata_uuid Anand Jain via Linux-f2fs-devel
2026-09-01 20:51   ` Zorro Lang via Linux-f2fs-devel
2026-08-31  7:17 ` [f2fs-dev] [PATCH v8 0/13] fstests: add test coverage for cloned filesystem ids Anand Suveer Jain via Linux-f2fs-devel

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=4226c2b6-d108-4666-9ac9-b52830b3fd50@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=asj@kernel.org \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox