Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: Vallimaharajan G <vallimaharajan(dot)gs(at)zohocorp(dot)com>
Cc: "zlabs-cstore(at)zohocorp(dot)com" <zlabs-cstore(at)zohocorp(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [Bug] Heap Use After Free in parallel_vacuum_reset_dead_items Function
Date: 2024-12-05 01:46:33
Message-ID: CANWCAZZgVMvByZA1r9mpPsHYnGrvX=HJR20H+5rbs3AnwvbfFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Tue, Nov 26, 2024 at 4:53 PM John Naylor <johncnaylorls(at)gmail(dot)com> 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Kemnitz 2024-12-05 02:12:36 Re: Tablespace storage bug...
Previous Message David G. Johnston 2024-12-05 01:09:29 Re: Tablespace storage bug...

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2024-12-05 02:03:50 Re: Disallow UPDATE/DELETE on table with unpublished generated column as REPLICA IDENTITY
Previous Message Masahiro Ikeda 2024-12-05 01:39:22 Re: Doc: clarify the log message level of the VERBOSE option