public inbox for [email protected]
help / color / mirror / Atom feedFrom: John Naylor <[email protected]>
To: Vallimaharajan G <[email protected]>
Cc: [email protected] <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function
Date: Thu, 5 Dec 2024 08:46:33 +0700
Message-ID: <CANWCAZZgVMvByZA1r9mpPsHYnGrvX=HJR20H+5rbs3AnwvbfFA@mail.gmail.com> (raw)
In-Reply-To: <CANWCAZYJe4vya4taNFdqK2dx6q3VmyxyL7V+8DBy62YnaQUeiA@mail.gmail.com>
References: <[email protected]>
<CANWCAZYJe4vya4taNFdqK2dx6q3VmyxyL7V+8DBy62YnaQUeiA@mail.gmail.com>
On Tue, Nov 26, 2024 at 4:53 PM John Naylor <[email protected]> wrote:
> Thanks for the report! I don't see any immediate evidence of deleterious effects, but it's still sloppy. To reduce risk going forward, I think we should always access this pointer via the struct rather than a separate copy, quick attempt attached.
[removing -bugs]
I looked again and changed a few more places for consistency, and committed.
--
John Naylor
Amazon Web Services
view thread (4+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function
In-Reply-To: <CANWCAZZgVMvByZA1r9mpPsHYnGrvX=HJR20H+5rbs3AnwvbfFA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox