public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
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 14:42:30 -0600	[thread overview]
Message-ID: <f62ed378-6dc7-4574-80fb-54b07f7bcf31@kernel.dk> (raw)
In-Reply-To: <875x0d2ij4.fsf@mailhost.krisman.be>

On 9/10/26 10:11 AM, Gabriel Krisman Bertazi wrote:
> 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.

That'd be great, thank you!

-- 
Jens Axboe


  reply	other threads:[~2026-09-10 20:42 UTC|newest]

Thread overview: 9+ 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
2026-09-10 20:42         ` Jens Axboe [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=f62ed378-6dc7-4574-80fb-54b07f7bcf31@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=krisman@suse.de \
    --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