From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] Followup pull request for io_uring for 6.2-rc5
Date: Sat, 21 Jan 2023 13:56:42 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Just a single fix for a regression that happened in this release due to
a poll change. Normally I would've just deferred it to next week, but
since the original fix got picked up by stable, I think it's better to
just send this one off separately.
The issue is around the poll race fix, and how it mistakenly also got
applied to multishot polling. Those don't need the race fix, and we
should not be doing any reissues for that case. Exhaustive test cases
were written and committed to the liburing regression suite for the
reported issue, and additions for similar issues.
Please pulL!
The following changes since commit 8579538c89e33ce78be2feb41e07489c8cbf8f31:
io_uring/msg_ring: fix remote queue to disabled ring (2023-01-20 09:49:34 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.2-2023-01-21
for you to fetch changes up to 8caa03f10bf92cb8657408a6ece6a8a73f96ce13:
io_uring/poll: don't reissue in case of poll race on multishot request (2023-01-20 15:11:54 -0700)
----------------------------------------------------------------
io_uring-6.2-2023-01-21
----------------------------------------------------------------
Jens Axboe (1):
io_uring/poll: don't reissue in case of poll race on multishot request
io_uring/poll.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
Jens Axboe
next reply other threads:[~2023-01-21 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 20:56 Jens Axboe [this message]
2023-01-22 0:35 ` [GIT PULL] Followup pull request for io_uring for 6.2-rc5 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