From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Avoid core dump after getpwuid_r failure.
Date: Sun, 08 Sep 2024 23:15:08 +0000
Message-ID: <E1snR7b-000CFD-PE@gemulon.postgresql.org> (raw)
Avoid core dump after getpwuid_r failure.
Looking up a nonexistent user ID would lead to a null pointer
dereference. That's unlikely to happen here, but perhaps
not impossible.
Thinko in commit 4d5111b3f, noticed by Coverity.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/2e62fa62d6745ba3bcb0a517d002aff1f3cdefb7
Modified Files
--------------
src/interfaces/libpq/fe-auth.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Avoid core dump after getpwuid_r failure.
In-Reply-To: <E1snR7b-000CFD-PE@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox