From: Jens Axboe <[email protected]>
To: [email protected]
Subject: [PATCH 0/3] send/recv bundle fixes
Date: Wed, 7 Aug 2024 19:47:26 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
Just three minor fixes for 6.11, all marked for stable as well. Two
of them fix a missing REQ_F_NEED_CLEANUP being set for recv and send,
and the last one fixes non-bundle sends potentially picking more than
one buffer. Only bundle sends should do that.
--
Jens Axboe
next reply other threads:[~2024-08-08 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 1:47 Jens Axboe [this message]
2024-08-08 1:47 ` [PATCH 1/3] io_uring/net: ensure expanded bundle recv gets marked for cleanup Jens Axboe
2024-08-08 1:47 ` [PATCH 2/3] io_uring/net: ensure expanded bundle send " Jens Axboe
2024-08-08 1:47 ` [PATCH 3/3] io_uring/net: don't pick multiple buffers for non-bundle send 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 \
[email protected] \
[email protected] \
[email protected] \
/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