This test checks if overlayfs hardlinks are preserved across copy up. Check if they are preserved also after copy up and mount cycle. Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx> --- tests/overlay/018 | 13 +++++++++++-- tests/overlay/018.out | 5 +++++ 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/tests/overlay/018 b/tests/overlay/018 index 7570a16..46097a9 100755 --- a/tests/overlay/018 +++ b/tests/overlay/018 @@ -96,11 +96,20 @@ cat $FILES record_ino_nlink $tmp.before # Modify content of one of the hardlinks -echo "one" >> $foo +# Intentionally modify the last hardlink in $FILES, so after mount cycle +# when reading the first file in $FILES, last file won't be in inode/dcache +echo "one" >> $bar echo "== After write one ==" cat $FILES -check_ino_nlink $tmp.before $tmp.after +check_ino_nlink $tmp.before $tmp.after_one + +# Verify that the hardlinks survive a mount cycle +_scratch_cycle_mount + +echo "== After mount cycle ==" +cat $FILES +check_ino_nlink $tmp.after_one $tmp.after_cycle status=0 exit diff --git a/tests/overlay/018.out b/tests/overlay/018.out index 784e8bc..5b74ee1 100644 --- a/tests/overlay/018.out +++ b/tests/overlay/018.out @@ -7,3 +7,8 @@ zero one zero one +== After mount cycle == +zero +one +zero +one -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
