From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sat, 23 Nov 2013 23:24:26 +0000 (-0500)
Subject: Ensure _dosmaperr() actually sets errno correctly.
X-Git-Tag: REL9_3_2~28
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=69eb861695be52706217ec58830178d0a82d53ce;p=postgresql

Ensure _dosmaperr() actually sets errno correctly.

If logging is enabled, either ereport() or fprintf() might stomp on errno
internally, causing this function to return the wrong result.  That might
only end in a misleading error report, but in any code that's examining
errno to decide what to do next, the consequences could be far graver.

This has been broken since the very first version of this file in 2006
... it's a bit astonishing that we didn't identify this long ago.

Reported by Amit Kapila, though this isn't his proposed fix.
---

diff --git a/src/port/win32error.c b/src/port/win32error.c
index 2222be8907..5c49b38a5e 100644
--- a/src/port/win32error.c
+++ b/src/port/win32error.c
@@ -179,14 +179,16 @@ _dosmaperr(unsigned long e)
 	{
 		if (doserrors[i].winerr == e)
 		{
-			errno = doserrors[i].doserr;
+			int			doserr = doserrors[i].doserr;
+
 #ifndef FRONTEND
 			ereport(DEBUG5,
 					(errmsg_internal("mapped win32 error code %lu to %d",
-									 e, errno)));
+									 e, doserr)));
 #elif FRONTEND_DEBUG
-			fprintf(stderr, _("mapped win32 error code %lu to %d"), e, errno);
+			fprintf(stderr, _("mapped win32 error code %lu to %d"), e, doserr);
 #endif
+			errno = doserr;
 			return;
 		}
 	}