summaryrefslogtreecommitdiff
path: root/selftest
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2021-04-19 16:25:51 -0700
committerAndreas Schneider <asn@cryptomilk.org>2021-04-20 07:39:37 +0000
commit249565c65af05fb88e15ed10d0ff770c97c938ff (patch)
treef6f0aabfcc5c62702a97a459649f2ac9b1ae58bb /selftest
parent25a2b7324bb615012571de566c1c7944ba1f4e58 (diff)
downloadsamba-249565c65af05fb88e15ed10d0ff770c97c938ff.tar.gz
s3: torture: Add samba3.smbtorture_s3.plain.POSIX-SYMLINK-CHMOD
Shows we must protect against a null fsp handle when doing POSIX chmod on a symlink, whether the symlink points to a real object or is dangling. Add to knownfail for now. Commit 9722732b1867e359304594ada72ff40cd1341be5 removed the fsp == NULL protection for POSIX, and we need to put it back. Signed-off-by: Jeremy Allison <jra@samba.org> Reviewed-by: Andreas Schneider <asn@samba.org>
Diffstat (limited to 'selftest')
-rw-r--r--selftest/knownfail.d/symlink_chmod2
1 files changed, 2 insertions, 0 deletions
diff --git a/selftest/knownfail.d/symlink_chmod b/selftest/knownfail.d/symlink_chmod
new file mode 100644
index 00000000000..8ebe2a7cf9e
--- /dev/null
+++ b/selftest/knownfail.d/symlink_chmod
@@ -0,0 +1,2 @@
+^samba3.smbtorture_s3.plain.*POSIX-SYMLINK-CHMOD
+^samba3.smbtorture_s3.crypt.*POSIX-SYMLINK-CHMOD