From: Zorro Lang <zlang@kernel.org>
To: Anand Jain <asj@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, djwong@kernel.org
Subject: Re: [PATCH v8 11/13] fstests: verify exportfs file handles on cloned filesystems
Date: Wed, 2 Sep 2026 04:30:29 +0800 [thread overview]
Message-ID: <apc1uPbA2hKofHA6@zlang-mailbox> (raw)
In-Reply-To: <7afe9c82cce1540ea0f8cc1f3d1306c24b6cc84d.1784949155.git.asj@kernel.org>
On Sat, Jul 25, 2026 at 03:39:08PM +0800, Anand Jain wrote:
> Ensure that exportfs can correctly decode file handles on a cloned
> filesystem across a mount cycle, by file handles generated on a
> cloned device remain valid after mount cycle.
>
> Signed-off-by: Anand Jain <asj@kernel.org>
> ---
> tests/generic/805 | 80 +++++++++++++++++++++++++++++++++++++++++++
> tests/generic/805.out | 2 ++
> 2 files changed, 82 insertions(+)
> create mode 100644 tests/generic/805
> create mode 100644 tests/generic/805.out
>
> diff --git a/tests/generic/805 b/tests/generic/805
> new file mode 100644
> index 000000000000..5827eee039df
> --- /dev/null
> +++ b/tests/generic/805
> @@ -0,0 +1,80 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2026 Anand Jain <asj@kernel.org>. All Rights Reserved.
> +#
> +# FS QA Test No. 805
> +# Verify that file handles encoded on a cloned filesystem remain valid and
> +# resolvable via open_by_handle across a mount cycle and mount order swap.
> +
> +. ./common/preamble
> +
> +_begin_fstest auto quick exportfs clone
> +
> +_require_test
> +_require_block_device $TEST_DEV
> +_require_exportfs
> +_require_loop
> +_require_test_program "open_by_handle"
> +
> +_cleanup()
> +{
> + cd /
> + rm -r -f $tmp.*
> + _unmount $mnt1 2>/dev/null
> + _unmount $mnt2 2>/dev/null
> + _loop_image_destroy "${devs[@]}" 2> /dev/null
> +}
> +
> +# Create test dir and test files, encode file handles and store to tmp file
> +create_test_files()
> +{
> + rm -rf $testdir
> + mkdir -p $testdir
> + $here/src/open_by_handle -cwp -o $tmp.handles_file $testdir $NUMFILES
> +}
> +
> +# Attempt to read and decode the saved file handles on the targeted mount point.
> +test_file_handles()
> +{
> + local opt=$1
> + local when=$2
> +
> + echo test_file_handles after $when
> + $here/src/open_by_handle $opt -i $tmp.handles_file $mnt2 $NUMFILES
> +}
> +
> +# Setup base loop device and its clone
> +devs=()
> +_loop_image_create_clone devs
> +mkdir -p $TEST_DIR/$seq
> +mnt1=$TEST_DIR/$seq/mnt1
> +mnt2=$TEST_DIR/$seq/mnt2
> +mkdir -p $mnt1
> +mkdir -p $mnt2
> +
> +# Mount both identical UUID filesystems simultaneously
> +_mount $(_common_dev_mount_options) $(_clone_mount_option) ${devs[0]} $mnt1 || \
> + _fail "Failed to mount dev1"
> +_mount $(_common_dev_mount_options) $(_clone_mount_option) ${devs[1]} $mnt2 || \
> + _fail "Failed to mount dev2"
> +
> +NUMFILES=1
NUMFILES=${LOAD_FACTOR} ?
> +testdir=$mnt2/testdir
> +
> +# Decode file handles of files/dir after cycle mount
> +create_test_files
> +
> +# Cycle mounts and reverse initialization sequence to check if
> +# file handle lookups are okay
> +_unmount $mnt1
> +_unmount $mnt2
> +_mount $(_common_dev_mount_options) $(_clone_mount_option) ${devs[1]} $mnt2 || \
> + _fail "Failed to mount dev2"
> +_mount $(_common_dev_mount_options) $(_clone_mount_option) ${devs[0]} $mnt1 || \
> + _fail "Failed to mount dev1"
> +
> +# Verify file handles can still be resolved post-mount-cycle
> +test_file_handles -rp "cycle mount"
> +
> +status=0
> +exit
> diff --git a/tests/generic/805.out b/tests/generic/805.out
> new file mode 100644
> index 000000000000..29b11ec77ffb
> --- /dev/null
> +++ b/tests/generic/805.out
> @@ -0,0 +1,2 @@
> +QA output created by 805
> +test_file_handles after cycle mount
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-09-01 20:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 7:38 [PATCH v8 0/13] fstests: add test coverage for cloned filesystem ids Anand Jain
2026-07-25 7:38 ` [PATCH v8 01/13] fstests: add _loop_image_create_clone() helper Anand Jain
2026-09-01 12:33 ` Zorro Lang
2026-09-01 13:52 ` Anand Suveer Jain
2026-07-25 7:38 ` [PATCH v8 02/13] fstests: add _clone_mount_option() helper Anand Jain
2026-09-01 12:39 ` Zorro Lang
2026-09-01 13:54 ` Anand Suveer Jain
2026-07-25 7:39 ` [PATCH v8 03/13] fstests: add FSNOTIFYWAIT_PROG Anand Jain
2026-09-01 15:37 ` Zorro Lang
2026-07-25 7:39 ` [PATCH v8 04/13] fstests: add _require_fanotify_function Anand Jain
2026-09-01 15:42 ` Zorro Lang
2026-09-01 22:39 ` Anand Suveer Jain
2026-07-25 7:39 ` [PATCH v8 05/13] fstests: add _require_unique_f_fsid() helper Anand Jain
2026-09-01 16:09 ` Zorro Lang
2026-09-01 23:32 ` Anand Suveer Jain
2026-07-25 7:39 ` [PATCH v8 06/13] fstests: add SEMANAGE_PROG Anand Jain
2026-07-25 7:39 ` [PATCH v8 07/13] fstests: verify fanotify isolation on cloned filesystems Anand Jain
2026-09-01 18:23 ` Zorro Lang
2026-09-04 6:14 ` Anand Suveer Jain
2026-07-25 7:39 ` [PATCH v8 08/13] fstests: verify f_fsid for " Anand Jain
2026-09-01 18:51 ` Zorro Lang
2026-07-25 7:39 ` [PATCH v8 09/13] fstests: verify libblkid resolution of duplicate UUIDs Anand Jain
2026-09-01 19:12 ` Zorro Lang
2026-07-25 7:39 ` [PATCH v8 10/13] fstests: verify IMA isolation on cloned filesystems Anand Jain
2026-09-01 19:58 ` Zorro Lang
2026-07-25 7:39 ` [PATCH v8 11/13] fstests: verify exportfs file handles " Anand Jain
2026-09-01 20:29 ` Zorro Lang
2026-09-01 20:30 ` Zorro Lang [this message]
2026-07-25 7:39 ` [PATCH v8 12/13] fstests: add _change_metadata_uuid helper Anand Jain
2026-09-01 20:53 ` Zorro Lang
2026-07-25 7:39 ` [PATCH v8 13/13] fstests: test UUID consistency for clones with metadata_uuid Anand Jain
2026-09-01 20:51 ` Zorro Lang
2026-08-31 7:17 ` [PATCH v8 0/13] fstests: add test coverage for cloned filesystem ids Anand Suveer 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=apc1uPbA2hKofHA6@zlang-mailbox \
--to=zlang@kernel.org \
--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-f2fs-devel@lists.sourceforge.net \
--cc=linux-xfs@vger.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