Align all comments to the term 'constant inode numbers' and explain why hardlinks are excluded from this test. Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx> --- tests/overlay/017 | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/tests/overlay/017 b/tests/overlay/017 index 7c1430d..e04690c 100755 --- a/tests/overlay/017 +++ b/tests/overlay/017 @@ -1,7 +1,7 @@ #! /bin/bash # FSQA Test No. 017 # -# Test unstable inode number +# Test constant inode numbers # # This simple test demonstrates a known issue with overlayfs: # - stat file A shows inode number X @@ -58,9 +58,8 @@ rm -f $seqres.full _scratch_mkfs >>$seqres.full 2>&1 # Create our test files. -# Not dealing with hardlinks here, because there is more to test -# then stable inode number. -# Hardlinks will get a test of their own. +# Not dealing with hardlinks here, when hardlinks are broken they +# should not preserve the inode number. lowerdir=$OVL_BASE_SCRATCH_MNT/$OVL_LOWER mkdir -p $lowerdir mkdir $lowerdir/dir -- 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
