Re: Fix uninitialized PruneFreezeResult in pruneheap and vacuumlazy - Mailing list pgsql-hackers

From Feilong Meng
Subject Re: Fix uninitialized PruneFreezeResult in pruneheap and vacuumlazy
Date
Msg-id tencent_F99BAF3F98799941EF31EEEE23E34A0B2F05@qq.com
Whole thread Raw
In response to Fix uninitialized PruneFreezeResult in pruneheap and vacuumlazy  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
Hi Chao Li,Hackers,

> PruneFreezeResult presult; <== here presult is not initialized

>   const PruneFreezeResult *presult, <== presult is a const pointer, so prune_freeze_setup won’t update its content
>   PruneState *prstate)
> {
>     prstate->deadoffsets = (OffsetNumber *) presult->deadoffsets; <== presult->deadoffsets could be a random value
> }
> ```

> Attached is a simple fix by just initializing presult in the first place with {0}. 

    Initializing ’presult‘ under my operating system is very effective.
    I have tested the change, and "make check" passed.


Best regards!


Original

From: Chao Li <li.evan.chao@gmail.com>
Date: 2025-12-11 12:02
To: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Subject: Fix uninitialized PruneFreezeResult in pruneheap and vacuumlazy

Hi Hackers,

While reviewing Melanie's patch [1], I found this bug where presult is not initialized. Let me explain the logic.

In the first place:
```
static int
lazy_scan_prune(LVRelState *vacrel,
Buffer buf,
BlockNumber blkno,
Page page,
Buffer vmbuffer,
bool all_visible_according_to_vm,
bool *has_lpdead_items,
bool *vm_page_frozen)
{
Relation rel = vacrel->rel;
PruneFreezeResult presult; <== here presult is not initialized

heap_page_prune_and_freeze(&params,
  &presult, <== uninitialized presult is passed into heap_page_prune_and_freeze
  &vacrel->offnum,
  &vacrel->NewRelfrozenXid, &vacrel->NewRelminMxid);
```

Then in heap_page_prune_and_freeze():
```
void
heap_page_prune_and_freeze(PruneFreezeParams *params,
  PruneFreezeResult *presult,
  OffsetNumber *off_loc,
  TransactionId *new_relfrozen_xid,
  MultiXactId *new_relmin_mxid)
{
Buffer buffer = params->buffer;
Page page = BufferGetPage(buffer);
PruneState prstate;
bool do_freeze;
bool do_prune;
bool do_hint_prune;
bool did_tuple_hint_fpi;
int64 fpi_before = pgWalUsage.wal_fpi;

/* Initialize prstate */
prune_freeze_setup(params,
  new_relfrozen_xid, new_relmin_mxid,
  presult, &prstate); <== immediately pass uninitialized presult to prune_freeze_setup
```

Then in prune_freeze_setup():
```
static void
prune_freeze_setup(PruneFreezeParams *params,
  TransactionId *new_relfrozen_xid,
  MultiXactId *new_relmin_mxid,
  const PruneFreezeResult *presult, <== presult is a const pointer, so prune_freeze_setup won’t update its content
  PruneState *prstate)
{
    prstate->deadoffsets = (OffsetNumber *) presult->deadoffsets; <== presult->deadoffsets could be a random value
}
```

Attached is a simple fix by just initializing presult in the first place with {0}. 


Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Docs: Standardize "cannot" usage in SGML source
Next
From: Ajit Awekar
Date:
Subject: Re: Periodic authorization expiration checks using GoAway message