From: Nyakundi Emmanuel <nyariboemmanuel8@gmail.com>
To: federico.brasili@gmail.com
Cc: axboe@kernel.dk, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nyakundi Emmanuel <nyariboemmanuel8@gmail.com>
Subject: Re: [BUG io_uring] Failed RECVSEND_BUNDLE can persistently shrink non-INC pbuf ring len and affect later READ operations
Date: Mon, 8 Jun 2026 00:22:18 +0300 [thread overview]
Message-ID: <nyakundi-confirm-recvsend-bundle-20260607@gmail.com> (raw)
In-Reply-To: <CAAEr8jZDdiYB2vp9VJzSqq2J-GssH8GhrLYYn_2W2KAjYwDzSQ@mail.gmail.com>
On Sun, 7 Jun 2026, Federico Brasili wrote:
> I found a reproducible io_uring provided-buffer ring issue on Ubuntu
> kernel 7.0.0-22-generic.
>
> A failed IORING_RECVSEND_BUNDLE receive on a non-INC provided-buffer
> ring can persistently shrink the user-visible buffer descriptor length.
Confirmed reproducible on:
Linux archlinux 7.0.11-arch1-1 #1 SMP PREEMPT_DYNAMIC
Tue, 02 Jun 2026 18:26:58 +0000 x86_64
Arch Linux (rolling)
Output from your reproducer, run unprivileged:
[INIT] entry0 len=4096 bid=0 entry1 len=4096 bid=1 tail=2
[STEP1] poison empty socket: BUNDLE len=1 expect -EAGAIN but entry0 len may truncate
[CQE1] res=-11 flags=0x0 user=0x1111
[AFTER1] entry0 len=1 entry1 len=4096 tail=2 changed_buf0=0 changed_buf1=0 guard_before=0 guard_after=0
[STEP2] wrote pipe bytes=4096, now IORING_OP_READ len=4096 after recv-BUNDLE poisoning
[CQE_READ] res=1 flags=0x1 user=0x6666
[AFTER_READ] entry0 len=1 entry1 len=4096 tail=2 changed_buf0=1 changed_buf1=0 guard_before=0 guard_after=0
[STEP3] wrote second pipe chunk bytes=4096, second IORING_OP_READ len=4096 without republish
[CQE_READ2] res=4096 flags=0x10001 user=0x7777
[AFTER_READ2] entry0 len=1 entry1 len=4096 tail=2 changed_buf0=1 changed_buf1=4096 guard_before=0 guard_after=0
entry0.len persistently corrupted 4096 -> 1 after -EAGAIN RECV_BUNDLE.
Subsequent IORING_OP_READ consumed the poisoned length as reported.
This confirms the issue is not Ubuntu-specific and reproduces on a
stock upstream-tracking kernel.
Nyakundi Emmanuel
next prev parent reply other threads:[~2026-06-07 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 11:41 [BUG io_uring] Failed RECVSEND_BUNDLE can persistently shrink non-INC pbuf ring len and affect later READ operations Federico Brasili
2026-06-07 19:07 ` Jens Axboe
2026-06-07 20:08 ` Federico Brasili
2026-06-07 21:22 ` Nyakundi Emmanuel [this message]
2026-06-07 21:39 ` Jens Axboe
2026-06-07 22:10 ` [PATCH] test/recv-bundle-pbuf-len-poison: add regression test for pbuf len corruption Nyakundi Emmanuel
2026-06-07 22:16 ` Jens Axboe
2026-06-07 21:38 ` [BUG io_uring] Failed RECVSEND_BUNDLE can persistently shrink non-INC pbuf ring len and affect later READ operations Jens Axboe
2026-06-07 21:52 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nyakundi-confirm-recvsend-bundle-20260607@gmail.com \
--to=nyariboemmanuel8@gmail.com \
--cc=axboe@kernel.dk \
--cc=federico.brasili@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox