From: Gabriel Krisman Bertazi <krisman@suse.de>
To: axboe@kernel.dk
Cc: io-uring@vger.kernel.org, Gabriel Krisman Bertazi <krisman@suse.de>
Subject: [PATCH 0/2] Fix return with MSG_TUNC overtruncating buffers
Date: Wed, 2 Sep 2026 20:00:39 -0300 [thread overview]
Message-ID: <20260902230041.1320658-1-krisman@suse.de> (raw)
Jens,
This is an attempt to fix the issue reported at [1]. It works by
splitting the return size (which can be the full size of the packet)
from the value actually commited in the buffer. Please, let me know
your thoughts. Patch 1 is a small preparation and patch 2 has the fix.
This was tested for regressions against liburing as well as using the
reproducer from the bug, which I can turn into a proper test case
against liburing.
I sent this before but the submission was botched. Please take this
version in consideration.
Thanks,
[1] https://github.com/axboe/liburing/issues/1619
Gabriel Krisman Bertazi (2):
io_uring/net: let io_recv_buf_select return the length of the buffer
region
io_uring/net: don't overconsume buffers when using MSG_TRUNC
io_uring/net.c | 48 +++++++++++++++++++++++++++++++++++++-----------
1 file changed, 37 insertions(+), 11 deletions(-)
--
2.55.0
next reply other threads:[~2026-09-02 23:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 23:00 Gabriel Krisman Bertazi [this message]
2026-09-02 23:00 ` [PATCH 1/2] io_uring/net: let io_recv_buf_select return the length of the buffer region Gabriel Krisman Bertazi
2026-09-02 23:00 ` [PATCH 2/2] io_uring/net: don't overconsume buffers when using MSG_TRUNC Gabriel Krisman Bertazi
2026-09-09 13:56 ` Jens Axboe
2026-09-09 13:58 ` Jens Axboe
2026-09-10 16:08 ` Gabriel Krisman Bertazi
2026-09-10 16:11 ` Gabriel Krisman Bertazi
2026-09-10 20:42 ` Jens Axboe
2026-09-10 15:18 ` [PATCH 0/2] Fix return with MSG_TUNC overtruncating buffers 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=20260902230041.1320658-1-krisman@suse.de \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=io-uring@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.