From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/2] io_uring/net: don't overconsume buffers when using MSG_TRUNC
Date: Thu, 10 Sep 2026 13:11:27 -0300 [thread overview]
Message-ID: <875x0d2ij4.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <87a4pp2iog.fsf@mailhost.krisman.be>
Gabriel Krisman Bertazi <krisman@suse.de> writes:
> I'm folding your fix up in the v3, modulo a compilation error. It only
> changes the error path, the bug is still fixed on 7.3 with your patch
> folded in.
Please scratch that. I misunderstood your previous email. I see you
applied it on io_uring-7.3 with your fix up. Looks good and the
test still passes. I'll turn it into a liburing test.
> Any suggestions on how to test this error path for liburing?
> I got a test for the bug, but testing ret<0 means failing the socket.
>
>
> --
> Gabriel Krisman Bertazi
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2026-09-10 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 23:00 [PATCH 0/2] Fix return with MSG_TUNC overtruncating buffers Gabriel Krisman Bertazi
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 [this message]
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=875x0d2ij4.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=stable@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