From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: fstests@vger.kernel.org, amir73il@gmail.com
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
linux-unionfs@vger.kernel.org, eguan@redhat.com
Subject: [PATCH 1/3] overlay/017: Remove constant st_ino/d_ino test for hardlinks
Date: Sat, 18 Nov 2017 11:28:02 +0530 [thread overview]
Message-ID: <20171118055804.17611-1-chandan@linux.vnet.ibm.com> (raw)
Constant st_ino/d_ino for hardlinks requires "index" config
feature/mount option to be enabled. overlay/018 already tests constant
st_ino feature for hardlinks. A future commit will add constant d_ino
test to overlay/018 test.
Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
---
tests/overlay/017 | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/tests/overlay/017 b/tests/overlay/017
index e9c8525..03955d0 100755
--- a/tests/overlay/017
+++ b/tests/overlay/017
@@ -72,10 +72,8 @@ mknod $lowerdir/chrdev c 1 1
mknod $lowerdir/blkdev b 1 1
mknod $lowerdir/fifo p
$here/src/af_unix $lowerdir/socket
-touch $lowerdir/hardlink1
-ln $lowerdir/hardlink1 $lowerdir/hardlink2
-FILES="dir file symlink chrdev blkdev fifo socket hardlink1 hardlink2"
+FILES="dir file symlink chrdev blkdev fifo socket"
# Record inode numbers in format <ino> <basename>
function record_inode_numbers()
--
2.9.5
next reply other threads:[~2017-11-18 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 5:58 Chandan Rajendra [this message]
2017-11-18 5:58 ` [PATCH 2/3] overlay/018: Add constant d_ino test Chandan Rajendra
2017-11-18 20:35 ` Amir Goldstein
2017-11-18 5:58 ` [PATCH 3/3] overlay: Test hardlink breakage on non-samefs setup Chandan Rajendra
2017-11-18 20:36 ` Amir Goldstein
2017-11-18 20:34 ` [PATCH 1/3] overlay/017: Remove constant st_ino/d_ino test for hardlinks Amir Goldstein
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=20171118055804.17611-1-chandan@linux.vnet.ibm.com \
--to=chandan@linux.vnet.ibm.com \
--cc=amir73il@gmail.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@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