diff options
| author | Volker Lendecke <vl@samba.org> | 2019-06-19 17:50:54 +0200 |
|---|---|---|
| committer | Jeremy Allison <jra@samba.org> | 2019-06-20 17:18:18 +0000 |
| commit | 3f6ed6e35239507ebe78091b9e1b4af7b644e3fd (patch) | |
| tree | 01a358f65ab47abbb0839db80895acc89bf801cb /selftest | |
| parent | b20231a1abb6d790dcb667f7010ec3b0b1ecb00b (diff) | |
| download | samba-3f6ed6e35239507ebe78091b9e1b4af7b644e3fd.tar.gz | |
torture3: Run a blocking lock&x call with a subsequent read
Samba aborts the read&x after a blocked, but eventually successful
locking&x call. Both Windows and source4/ntvfs do the read properly,
source3/smbd does not. With later code, this will become possible much
easier. Lets see if it's worth it given that we've got away with this
forever.
Signed-off-by: Volker Lendecke <vl@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
Diffstat (limited to 'selftest')
| -rw-r--r-- | selftest/knownfail | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/selftest/knownfail b/selftest/knownfail index 3f62bb5047a..7b5d2ba7509 100644 --- a/selftest/knownfail +++ b/selftest/knownfail @@ -15,6 +15,8 @@ ^samba3.smbtorture_s3.crypt_server # expected to give ACCESS_DENIED as SMB1 encryption isn't used ^samba3.smbtorture_s3.*.LOCK10.*\(fileserver\) ^samba3.smbtorture_s3.*.LOCK10.*\(nt4_dc\) +^samba3.smbtorture_s3.*.LOCK12.*\(fileserver\) +^samba3.smbtorture_s3.*.LOCK12.*\(nt4_dc\) ^samba3.nbt.dgram.*netlogon2\(nt4_dc\) ^samba3.*rap.sam.*.useradd # Not provided by Samba 3 ^samba3.*rap.sam.*.userdelete # Not provided by Samba 3 |