[acl] incorrectly checking args for setacl

in getacl, the output goes into the userbuffer and thus can't be null.

in setacl, the input comes from setsecurity.securitydescriptor not
userbuffer.
This commit is contained in:
Olga Kornievskaia 2012-05-15 16:21:24 -04:00
parent 70ab983f15
commit 192a502785

View file

@ -5066,9 +5066,6 @@ NTSTATUS check_nfs41_setacl_args(
status = STATUS_NOT_SUPPORTED; status = STATUS_NOT_SUPPORTED;
goto out; goto out;
} }
if (RxContext->CurrentIrp->UserBuffer == NULL &&
RxContext->CurrentIrpSp->Parameters.QuerySecurity.Length)
status = STATUS_INVALID_USER_BUFFER;
out: out:
return status; return status;
} }