s3:error_map: make NTSTATUS -> errno -> NTSTATUS mapping consistent for NT_STATUS_INV...

Why have we mapped EINVAL -> NT_STATUS_INVALID_HANDLE before?

metze

diff --git a/source3/lib/errmap_unix.c b/source3/lib/errmap_unix.c
index d43598bc53f378194d975ff35f81ad42f5ac5ac9..d5b94e998579f6606c784090c4bd1a55d7a86359 100644 (file)
--- a/source3/lib/errmap_unix.c
+++ b/source3/lib/errmap_unix.c
@@ -31,7 +31,7 @@ const struct unix_error_map unix_dos_nt_errmap[] = {
        { ENOTDIR, ERRDOS, ERRbadpath,  NT_STATUS_NOT_A_DIRECTORY },
        { EIO, ERRHRD, ERRgeneral, NT_STATUS_IO_DEVICE_ERROR },
        { EBADF, ERRSRV, ERRsrverror, NT_STATUS_INVALID_HANDLE },
-       { EINVAL, ERRSRV, ERRsrverror, NT_STATUS_INVALID_HANDLE },
+       { EINVAL, ERRSRV, ERRsrverror, NT_STATUS_INVALID_PARAMETER },
        { EEXIST, ERRDOS, ERRfilexists, NT_STATUS_OBJECT_NAME_COLLISION},
        { ENFILE, ERRDOS, ERRnofids, NT_STATUS_TOO_MANY_OPENED_FILES },
        { EMFILE, ERRDOS, ERRnofids, NT_STATUS_TOO_MANY_OPENED_FILES },