After recently upgrading the xfs and xfsprogs trees I get reproducible xfs/103 failures because the n flags is not reported. Does anyone else see this? root@testvm:~/xfstests# diff -u tests/xfs/103.out /root/xfstests/results//xfs/103 --- tests/xfs/103.outs# 2016-03-29 13:59:30.451720622 +0000stests/results//xfs/10 +++ /root/xfstests/results//xfs/103.out.bad 2016-11-12 16:30:37.032780388 +0000 @@ -3,7 +3,7 @@ *** mount *** testing nosymlinks directories *** setting nosymlinks bit ---n-- SCRATCH_MNT/nosymlink +----- SCRATCH_MNT/nosymlink ln: creating symbolic link 'SCRATCH_MNT/nosymlink/target': Operation not permitted *** 1st listing... SCRATCH_MNT -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
