Re: BUG #19796: io_uring crashes with specific kernel/liburing versions + io_max_concurrency due to rings overlap

From: Andres Freund <andres(at)anarazel(dot)de>
To: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19796: io_uring crashes with specific kernel/liburing versions + io_max_concurrency due to rings overlap
Date: 2026-10-26 13:31:48
Message-ID: 6vslel7zkhys66hsth6mod6g5j7cknio5olmcmu5iz4u6vu7xb@oad5obqok6u6
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2026-10-25 07:00:02 +0000, PG Bug reporting form wrote:
> I observed this on Ubuntu machines with kernels:
> Linux a 7.0.0-1014-aws #14~24.04.1-Ubuntu SMP PREEMPT Fri Sep 18 21:50:22
> UTC 2026 aarch64 aarch64 aarch64 GNU/Linux
> Linux b 6.14.1-061401-generic #202504071048 SMP PREEMPT_DYNAMIC Mon Apr 7
> 11:20:41 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
> and liburing 2.5. The issue is not reproduced after
> https://github.com/axboe/liburing/commit/9f4464d.

Seems we either could error out on buggy liburings or we could just add
64bytes to the ring sizes for those versions. I assume the latter fixes the
problem for you?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jan Nidzwetzki 2026-10-26 15:26:55 Re: START_REPLICATION silently truncates an overlong LSN component
Previous Message Andres Freund 2026-10-26 13:27:28 Re: BUG #19796: io_uring crashes with specific kernel/liburing versions + io_max_concurrency due to rings overlap