From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.4-final
Date: Wed, 21 Jun 2023 20:19:04 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A fix for a race condition with poll removal and linked timeouts, and
then a few followup fixes/tweaks for the msg_control patch from last
week. Not super important, particularly the sparse fixup, as it was
broken before that recent commit. But let's get it sorted for real for
this release, rather than just have it broken a bit differently.
Please pull!
The following changes since commit adeaa3f290ecf7f6a6a5c53219a4686cbdff5fbd:
io_uring/io-wq: clear current->worker_private on exit (2023-06-14 12:54:55 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.4-2023-06-21
for you to fetch changes up to 26fed83653d0154704cadb7afc418f315c7ac1f0:
io_uring/net: use the correct msghdr union member in io_sendmsg_copy_hdr (2023-06-21 07:34:17 -0600)
----------------------------------------------------------------
io_uring-6.4-2023-06-21
----------------------------------------------------------------
Jens Axboe (4):
io_uring/poll: serialize poll linked timer start with poll removal
io_uring/net: clear msg_controllen on partial sendmsg retry
io_uring/net: disable partial retries for recvmsg with cmsg
io_uring/net: use the correct msghdr union member in io_sendmsg_copy_hdr
io_uring/net.c | 17 +++++++++++------
io_uring/poll.c | 9 ++++-----
2 files changed, 15 insertions(+), 11 deletions(-)
--
Jens Axboe
next reply other threads:[~2023-06-22 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 2:19 Jens Axboe [this message]
2023-06-23 1:03 ` [GIT PULL] io_uring fixes for 6.4-final pr-tracker-bot
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] \
[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