Overlayfs directory inodes are constant across copy up, but not persistent on mount cycle. Compare the inode numbers before and after mount cycle. Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx> --- tests/overlay/017 | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/tests/overlay/017 b/tests/overlay/017 index 1cf684d..fe66f4c 100755 --- a/tests/overlay/017 +++ b/tests/overlay/017 @@ -9,7 +9,8 @@ # - stat file A shows inode number Y != X # # Also test if d_ino of readdir entries changes after copy up -# and if inode numbers persist after rename and drop caches. +# and if inode numbers persist after rename, drop caches and +# mount cycle. # #----------------------------------------------------------------------- # @@ -133,6 +134,19 @@ done diff -u $tmp.before $tmp.after_copyup diff -u $tmp.after_copyup $tmp.after_move +# Verify that the inode numbers survive a mount cycle +_scratch_cycle_mount + +record_inode_numbers $testdir $tmp.after_cycle + +cat $tmp.after_move | while read ino f; do + find $testdir/ -inum $ino -maxdepth 1 | grep -q $f || \ + echo "$f not found by ino $ino" +done + +# Compare before..after - expect silence +diff -u $tmp.after_move $tmp.after_cycle + echo "Silence is golden" status=0 exit -- 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
