Fix unsafe usage of strerror(errno) within ereport().

tglsfdc · tglsfdc · commit 28782d7e3b92 · 2018-05-21T00:32:39.000-04:00
This is the converse of the unsafe-usage-of-%m problem: the reason
ereport/elog provide that format code is mainly to dodge the hazard
of errno getting changed before control reaches functions within the
arguments of the macro.  I only found one instance of this hazard,
but it's been there since 9.4 :-(.
diff --git a/src/backend/libpq/auth.c b/src/backend/libpq/auth.c
@@ -2017,10 +2017,12 @@ auth_peer(hbaPort *port)
 	pw = getpwuid(uid);
 	if (!pw)
 	{
+		int			save_errno = errno;
+
 		ereport(LOG,
 				(errmsg("could not look up local user ID %ld: %s",
 						(long) uid,
-						errno ? strerror(errno) : _("user does not exist"))));
+						save_errno ? strerror(save_errno) : _("user does not exist"))));
 		return STATUS_ERROR;
 	}
 

Original file line number	Diff line number	Diff line change
`@@ -2017,10 +2017,12 @@ auth_peer(hbaPort *port)`
`2017`	`2017`	`pw = getpwuid(uid);`
`2018`	`2018`	`if (!pw)`
`2019`	`2019`	`{`
	`2020`	`+ int save_errno = errno;`
	`2021`	`+`
`2020`	`2022`	`ereport(LOG,`
`2021`	`2023`	`(errmsg("could not look up local user ID %ld: %s",`
`2022`	`2024`	`(long) uid,`
`2023`		`- errno ? strerror(errno) : _("user does not exist"))));`
	`2025`	`+ save_errno ? strerror(save_errno) : _("user does not exist"))));`
`2024`	`2026`	`return STATUS_ERROR;`
`2025`	`2027`	`}`
`2026`	`2028`