summaryrefslogtreecommitdiff
path: root/selftest
diff options
context:
space:
mode:
authorRalph Boehme <slow@samba.org>2019-05-06 14:14:26 +0200
committerJeremy Allison <jra@samba.org>2019-08-08 20:24:33 +0000
commita5e705504bf5a9cade2e57a18b068f654fa27a32 (patch)
tree596716f788bd35f44d99457d4dd5a2853602ca17 /selftest
parent63366996879fab5b1729de6d6224ca167bdb05b0 (diff)
downloadsamba-a5e705504bf5a9cade2e57a18b068f654fa27a32.tar.gz
s3:mdssvc: failing the RPC request if the mdssvc policy handle is not found
Turns out macOS mdssvc doesn't fail the RPC request if the policy handle is all zero. Also, if it fails with a non-all-zero handle, it returns a different RPC error, namely DCERPC_NCA_S_PROTO_ERROR, not DCERPC_FAULT_CONTEXT_MISMATCH (or rather their mapped NT_STATUS codes). Signed-off-by: Ralph Boehme <slow@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org>
Diffstat (limited to 'selftest')
-rw-r--r--selftest/knownfail.d/samba3.rpc4
1 files changed, 0 insertions, 4 deletions
diff --git a/selftest/knownfail.d/samba3.rpc b/selftest/knownfail.d/samba3.rpc
index 2b9179863c8..bafc9c3ece0 100644
--- a/selftest/knownfail.d/samba3.rpc
+++ b/selftest/knownfail.d/samba3.rpc
@@ -1,6 +1,2 @@
^samba3.rpc.mdssvc.rpccmd.close\(fileserver\)
-^samba3.rpc.mdssvc.rpccmd.null_ph\(fileserver\)
-^samba3.rpc.mdssvc.disconnect1.invalid_ph_unknown1\(fileserver\)
-^samba3.rpc.mdssvc.disconnect2.invalid_ph_cmd\(fileserver\)
-^samba3.rpc.mdssvc.disconnect3.invalid_ph_close\(fileserver\)
^samba3.rpc.mdssvc.mdscmd.fetch_unknown_cnid\(fileserver\)