diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2024-04-01 15:15:03 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2024-04-01 15:15:03 -0400 |
| commit | 30fe8a7ba07efc84caba06bce536c0a273ef5655 (patch) | |
| tree | 6a2a10aacca1f60cd667d0a03728f0951be27d0e /src/interfaces/libpq/fe-secure-openssl.c | |
| parent | 25675c474292dca71470ef17ea8a53c150eb0e0a (diff) | |
| download | postgresql-30fe8a7ba07efc84caba06bce536c0a273ef5655.tar.gz postgresql-30fe8a7ba07efc84caba06bce536c0a273ef5655.zip | |
Avoid possible longjmp-induced logic error in PLy_trigger_build_args.
The "pltargs" variable wasn't marked volatile, which makes it unsafe
to change its value within the PG_TRY block. It looks like the worst
outcome would be to fail to release a refcount on Py_None during an
(improbable) error exit, which would likely go unnoticed in the field.
Still, it's a bug. A one-liner fix could be to mark pltargs volatile,
but on the whole it seems cleaner to arrange things so that we don't
change its value within PG_TRY.
Per report from Xing Guo. This has been there for quite awhile,
so back-patch to all supported branches.
Discussion: https://postgr.es/m/CACpMh+DLrk=fDv07MNpBT4J413fDAm+gmMXgi8cjPONE+jvzuw@mail.gmail.com
Diffstat (limited to 'src/interfaces/libpq/fe-secure-openssl.c')
0 files changed, 0 insertions, 0 deletions