r8121: yuck. w2k3 seems to choose ERRDOS:ERRbaduid or

NT_STATUS_INVALID_HANDLE on a per call basis for a bad vuid. That
means it is doing checking for a valid vuid in each backend function,
rather than globally. I don't want to emulate that as it is way too
error prone, and could easily lead to a security hole, so instead
accept either error code in our test suite.
(This used to be commit aefa9e53fa97551c1b15bdd50565881e63aea9a8)

diff --git a/source4/torture/torture.c b/source4/torture/torture.c
index d7dbbc43cf1753a4f4e11880c8f1dcbf81304e32..935d1211e17bd2284ad5afd2a8f8bc5c9b6104ac 100644 (file)
--- a/source4/torture/torture.c
+++ b/source4/torture/torture.c
@@ -1347,7 +1347,9 @@ static BOOL run_vuidtest(void)
        }
 
        if (!NT_STATUS_EQUAL(cli->transport->error.e.nt_status, 
-                            NT_STATUS_DOS(ERRSRV, ERRbaduid))) {
+                            NT_STATUS_DOS(ERRSRV, ERRbaduid)) &&
+           !NT_STATUS_EQUAL(cli->transport->error.e.nt_status, 
+                            NT_STATUS_INVALID_HANDLE)) {
                printf("ERROR: qfileinfo should have returned DOS error "
                       "ERRSRV:ERRbaduid\n  but returned %s\n",
                       smbcli_errstr(cli->tree));