From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.1-rc6
Date: Fri, 18 Nov 2022 15:43:24 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Fixes for io_uring that should go into the 6.1 kernel release. This is
mostly fixing issues around the poll rework, but also two tweaks for the
multishot handling for accept and receive. All stable material.
Please pull!
The following changes since commit 5576035f15dfcc6cb1cec236db40c2c0733b0ba4:
io_uring/poll: lockdep annote io_poll_req_insert_locked (2022-11-11 09:59:27 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.1-2022-11-18
for you to fetch changes up to 7fdbc5f014c3f71bc44673a2d6c5bb2d12d45f25:
io_uring: disallow self-propelled ring polling (2022-11-18 09:29:31 -0700)
----------------------------------------------------------------
io_uring-6.1-2022-11-18
----------------------------------------------------------------
Pavel Begunkov (5):
io_uring: update res mask in io_poll_check_events
io_uring: fix tw losing poll events
io_uring: fix multishot accept request leaks
io_uring: fix multishot recv request leaks
io_uring: disallow self-propelled ring polling
include/linux/io_uring.h | 3 +++
io_uring/io_uring.c | 2 +-
io_uring/io_uring.h | 4 ++--
io_uring/net.c | 23 +++++++++--------------
io_uring/poll.c | 12 ++++++++++++
5 files changed, 27 insertions(+), 17 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-11-18 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 22:43 Jens Axboe [this message]
2022-11-19 1:24 ` [GIT PULL] io_uring fixes for 6.1-rc6 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-11-26 0:19 Jens Axboe
2022-11-26 2:25 ` 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