diff options
| author | Andres Freund <andres@anarazel.de> | 2025-03-26 16:06:54 -0400 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2025-03-26 16:06:54 -0400 |
| commit | 96da9050a57aece4a48ab34a84bc3b3412708a20 (patch) | |
| tree | db94f67398834e9f1d1dd2fb4038b31c8643d635 /src/backend/access/gist | |
| parent | 47a1f076a7c9789134a29dc738db0152e5f71b4c (diff) | |
| download | postgresql-96da9050a57aece4a48ab34a84bc3b3412708a20.tar.gz postgresql-96da9050a57aece4a48ab34a84bc3b3412708a20.zip | |
aio: Be more paranoid about interrupts
As reported by Noah, it's possible, although practically very unlikely, that
interrupts could be processed in between pgaio_io_reopen() and
pgaio_io_perform_synchronously(). Prevent that by explicitly holding
interrupts.
It also seems good to add an assertion to pgaio_io_before_prep() to ensure
that interrupts are held, as otherwise FDs referenced by the IO could be
closed during interrupt processing. All code in the aio series currently runs
the code with interrupts held, but it seems better to be paranoid.
Reviewed-by: Noah Misch <noah@leadboat.com>
Reported-by: Noah Misch <noah@leadboat.com>
Discussion: https://postgr.es/m/20250324002939.5c.nmisch@google.com
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions