From: Amir Goldstein <amir73il@gmail.com>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: Eryu Guan <eguan@redhat.com>, Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 3/3] overlay/041: use user defined overlay mount option
Date: Sun, 19 Nov 2017 13:56:29 +0200 [thread overview]
Message-ID: <1511092589-29179-4-git-send-email-amir73il@gmail.com> (raw)
In-Reply-To: <1511092589-29179-1-git-send-email-amir73il@gmail.com>
Mount non-samefs dirs with OVERLAY_MOUNT_OPTIONS, so user can opt-in
for constant inode numbers on non-samefs setup (i.e. -o xino) when it
is implemented.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
tests/overlay/041 | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tests/overlay/041 b/tests/overlay/041
index 11efacb..4152107 100755
--- a/tests/overlay/041
+++ b/tests/overlay/041
@@ -68,7 +68,8 @@ _scratch_mkfs
upperdir=$OVL_BASE_SCRATCH_MNT/$OVL_UPPER
workdir=$OVL_BASE_SCRATCH_MNT/$OVL_WORK
-_overlay_scratch_mount_dirs $lowerdir $upperdir $workdir
+_overlay_scratch_mount_dirs $lowerdir $upperdir $workdir \
+ $OVERLAY_MOUNT_OPTIONS
test_dir=$SCRATCH_MNT/test_dir/
@@ -184,7 +185,8 @@ _scratch_mkfs
upperdir=$OVL_BASE_SCRATCH_MNT/ovl-upper
workdir=$OVL_BASE_SCRATCH_MNT/ovl-work
-_overlay_scratch_mount_dirs $middir:$lowerdir $upperdir $workdir
+_overlay_scratch_mount_dirs $middir:$lowerdir $upperdir $workdir \
+ $OVERLAY_MOUNT_OPTIONS
# Copy up test_dir
touch $test_dir/test_file
--
2.7.4
next prev parent reply other threads:[~2017-11-19 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 11:56 [PATCH 0/3] More nonsamefs d_ino test cleanups Amir Goldstein
2017-11-19 11:56 ` [PATCH 1/3] overlay/041: code cleanup Amir Goldstein
2017-11-19 11:56 ` [PATCH 2/3] overlay/041: test consistent values of st_ino/d_ino for subdirs Amir Goldstein
2017-11-19 11:56 ` Amir Goldstein [this message]
2017-11-20 8:58 ` [PATCH 0/3] More nonsamefs d_ino test cleanups Chandan Rajendra
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=1511092589-29179-4-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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;
as well as URLs for NNTP newsgroup(s).