From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH v3 4/7] overlay/018: test lower hardlinks re-unite on copy up
Date: Wed, 5 Jul 2017 15:02:03 +0300 [thread overview]
Message-ID: <1499256126-21866-5-git-send-email-amir73il@gmail.com> (raw)
In-Reply-To: <1499256126-21866-1-git-send-email-amir73il@gmail.com>
Test that when two lower hardlinks are copied up, they end up
as two upper hardlinks of the same upper inode.
Drop caches before copy up so there is no knowledge of the
copied up hardlink in inode/dcache.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
tests/overlay/018 | 10 ++++++++++
tests/overlay/018.out | 7 +++++++
2 files changed, 17 insertions(+)
diff --git a/tests/overlay/018 b/tests/overlay/018
index 46097a9..41855dc 100755
--- a/tests/overlay/018
+++ b/tests/overlay/018
@@ -111,5 +111,15 @@ echo "== After mount cycle =="
cat $FILES
check_ino_nlink $tmp.after_one $tmp.after_cycle
+# Drop caches to get the copied up hardlink out of cache
+echo 3 > /proc/sys/vm/drop_caches
+
+# Modify content of the other hardlink
+echo "two" >> $foo
+
+echo "== After write two =="
+cat $FILES
+check_ino_nlink $tmp.after_one $tmp.after_two
+
status=0
exit
diff --git a/tests/overlay/018.out b/tests/overlay/018.out
index 5b74ee1..adc7f72 100644
--- a/tests/overlay/018.out
+++ b/tests/overlay/018.out
@@ -12,3 +12,10 @@ zero
one
zero
one
+== After write two ==
+zero
+one
+two
+zero
+one
+two
--
2.7.4
next prev parent reply other threads:[~2017-07-05 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 12:01 [PATCH v3 0/7] overlay hardlink tests Amir Goldstein
2017-07-05 12:02 ` [PATCH v3 1/7] overlay/018: re-factor and add to hardlink group Amir Goldstein
2017-07-05 12:02 ` [PATCH v3 2/7] overlay/018: print hardlink content to golden output Amir Goldstein
2017-07-05 12:02 ` [PATCH v3 3/7] overlay/018: test broken hardlinks after mount cycle Amir Goldstein
2017-07-05 12:02 ` Amir Goldstein [this message]
2017-07-05 12:02 ` [PATCH v3 5/7] overlay: test concurrent copy up of lower hardlinks Amir Goldstein
2017-07-05 12:02 ` [PATCH v3 6/7] overlay: test nlink accounting of overlay hardlinks Amir Goldstein
2017-07-05 12:02 ` [PATCH v3 7/7] overlay: test dropping nlink below zero 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=1499256126-21866-5-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.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