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 | d96f72569743842eb3d0cf4e97a77427b2729f38 (patch) | |
| tree | 43e2bc7f3be918cd6b4dabc639d4ee3fca15151f /src/interfaces/libpq/fe-secure-openssl.c | |
| parent | 0d30e48c2578a6857aa2869f1b2696b6eb5fef68 (diff) | |
| download | postgresql-d96f72569743842eb3d0cf4e97a77427b2729f38.tar.gz postgresql-d96f72569743842eb3d0cf4e97a77427b2729f38.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