From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fix for 6.14 final
Date: Sat, 22 Mar 2025 11:14:47 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Just a single fix for the commit that went into your tree yesterday,
which exposed an issue with not always clearing notifications. That
could cause them to be used more than once.
Please pull!
The following changes since commit cc34d8330e036b6bffa88db9ea537bae6b03948f:
io_uring/net: don't clear REQ_F_NEED_CLEANUP unconditionally (2025-03-20 12:27:27 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.14-20250322
for you to fetch changes up to 67c007d6c12da3e456c005083696c20d4498ae72:
io_uring/net: fix sendzc double notif flush (2025-03-22 08:14:36 -0600)
----------------------------------------------------------------
io_uring-6.14-20250322
----------------------------------------------------------------
Pavel Begunkov (1):
io_uring/net: fix sendzc double notif flush
io_uring/net.c | 2 ++
1 file changed, 2 insertions(+)
--
Jens Axboe
next reply other threads:[~2025-03-22 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 17:14 Jens Axboe [this message]
2025-03-22 21:45 ` [GIT PULL] io_uring fix for 6.14 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