]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE
authorJens Axboe <axboe@kernel.dk>
Tue, 21 Apr 2026 19:24:33 +0000 (13:24 -0600)
committerJens Axboe <axboe@kernel.dk>
Wed, 22 Apr 2026 01:18:34 +0000 (19:18 -0600)
commit1967f0b1cafdde37aa9e08e6021c14bcc484b7a5
tree00e784f7db414aadc5fdf80c57da395a635f473d
parent770594e78c3964cf23cf5287f849437cdde9b7d0
io_uring/poll: ensure EPOLL_ONESHOT is propagated for EPOLL_URING_WAKE

Commit:

aacf2f9f382c ("io_uring: fix req->apoll_events")

fixed an issue where poll->events and req->apoll_events weren't
synchronized, but then when the commit referenced in Fixes got added,
it didn't ensure the same thing.

If we mask in EPOLLONESHOT in the regular EPOLL_URING_WAKE path, then
ensure it's done for both. Including a link to the original report
below, even though it's mostly nonsense. But it includes a reproducer
that does show that IORING_CQE_F_MORE is set in the previous CQE,
while no more CQEs will be generated for this request. Just ignore
anything that pretends this is security related in any way, it's just
the typical AI nonsense.

Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/io-uring/CAM0zi7yQzF3eKncgHo4iVM5yFLAjsiob_ucqyWKs=hyd_GqiMg@mail.gmail.com/
Reported-by: Azizcan Daştan <azizcan.d@mileniumsec.com>
Fixes: 4464853277d0 ("io_uring: pass in EPOLL_URING_WAKE for eventfd signaling and wakeups")
Signed-off-by: Jens Axboe <axboe@kernel.dk>
io_uring/poll.c