From: Jens Axboe <axboe@kernel.dk>
To: Kai Aizen <kai.aizen.dev@gmail.com>, stable@vger.kernel.org
Cc: gregkh@linuxfoundation.org, io-uring@vger.kernel.org
Subject: Re: [PATCH stable] io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE
Date: Fri, 1 May 2026 16:56:18 -0600 [thread overview]
Message-ID: <3f1b30e7-d6a4-4e77-a05c-6d041f93824e@kernel.dk> (raw)
In-Reply-To: <20260501225250.90152-4-kai.aizen.dev@gmail.com>
On 5/1/26 4:51 PM, Kai Aizen wrote:
> From: Jens Axboe <axboe@kernel.dk>
>
> [ Upstream commit 1967f0b1cafdde37aa9e08e6021c14bcc484b7a5 ]
>
> Commit aacf2f9f382c ("io_uring: fix req->apoll_events") addressed
> synchronization issues between poll->events and req->apoll_events.
> However, a subsequent commit failed to maintain this consistency in the
> EPOLL_URING_WAKE code path.
>
> The patch ensures that when EPOLLONESHOT is set during regular
> EPOLL_URING_WAKE handling, it's applied to both poll->events and
> req->apoll_events. This prevents a condition where "IORING_CQE_F_MORE
> is set in the previous CQE, while no more CQEs will be generated for
> this request."
>
> Backport notes:
> This patch applies cleanly and identically to linux-6.18.y,
> linux-6.12.y, linux-6.6.y, and linux-6.1.y. The io_poll_wake()
> EPOLL_URING_WAKE branch is byte-identical to the upstream pre-patch
> state across all four trees.
OK with me, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2026-05-01 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 22:51 [PATCH 6.12.y] io_uring/poll: fix multishot recv missing EOF on wakeup race Kai Aizen
2026-05-01 22:51 ` [PATCH 6.6.y] " Kai Aizen
2026-05-01 22:51 ` [PATCH 6.1.y] " Kai Aizen
2026-05-01 22:51 ` [PATCH stable] io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE Kai Aizen
2026-05-01 22:56 ` Jens Axboe [this message]
2026-05-01 22:55 ` [PATCH 6.12.y] io_uring/poll: fix multishot recv missing EOF on wakeup race Jens Axboe
2026-05-02 6:29 ` Greg KH
2026-05-02 14:01 ` Jens Axboe
2026-05-03 18:19 ` [PATCH 6.12.y/6.6.y/6.1.y] " Sasha Levin
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 \
--in-reply-to=3f1b30e7-d6a4-4e77-a05c-6d041f93824e@kernel.dk \
--to=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=kai.aizen.dev@gmail.com \
--cc=stable@vger.kernel.org \
/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