From 58f1eb3986c41589e243a28e8ae94334a8bc89c3 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Tue, 18 Aug 2009 11:32:37 +0200 Subject: [PATCH] s3:error_map: make NTSTATUS -> errno -> NTSTATUS mapping consistent for NT_STATUS_INVALID_PARAMETER Why have we mapped EINVAL -> NT_STATUS_INVALID_HANDLE before? metze --- source3/lib/errmap_unix.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source3/lib/errmap_unix.c b/source3/lib/errmap_unix.c index d43598bc53f3..d5b94e998579 100644 --- 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 }, -- 2.34.1