From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
cve@kernel.org,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>
Subject: Re: proposed io_uring CVEs for 7.3.2
Date: Thu, 19 Nov 2026 18:54:16 -0500 [thread overview]
Message-ID: <20261119235416.1681888-1-sashal@kernel.org> (raw)
In-Reply-To: <fb339d39-d4f9-42ef-80b5-fab7398d2774@kernel.dk>
On Thu, Nov 19, 2026 at 10:40:24AM -0700, Jens Axboe wrote:
>> f013b6955064 io_uring/sqpoll: do the return-to-userspace work in the SQPOLL thread
>
>Reject, it just runs limits later than it should, they are still honored.
Agreed, this one makes sense to reject.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-19 23:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:22 Subject: io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04) dev
2026-11-14 2:00 ` Greg KH
2026-11-15 1:13 ` dev
2026-11-14 17:42 ` Sasha Levin
2026-11-14 18:12 ` Jens Axboe
2026-11-16 9:52 ` Greg Kroah-Hartman
2026-11-17 2:21 ` Jens Axboe
2026-11-17 7:42 ` Greg Kroah-Hartman
2026-11-17 12:41 ` Jens Axboe
2026-11-19 14:19 ` proposed io_uring CVEs for 7.3.2 Greg Kroah-Hartman
2026-11-19 15:32 ` Greg Kroah-Hartman
2026-11-19 17:40 ` Jens Axboe
2026-11-19 23:54 ` Sasha Levin [this message]
2026-11-20 6:58 ` Greg Kroah-Hartman
2026-11-19 17:39 ` Jens Axboe
2026-11-19 23:55 ` Sasha Levin
2026-11-20 7:01 ` Greg Kroah-Hartman
2026-11-17 12:42 ` io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04) Sasha Levin
2026-11-17 12:45 ` Jens Axboe
2026-11-17 12:59 ` Sasha Levin
2026-11-19 18:10 ` Jens Axboe
2026-11-19 20:39 ` Sasha Levin
2026-11-19 23:25 ` Jens Axboe
2026-11-20 5:17 ` Greg Kroah-Hartman
2026-11-20 20:39 ` 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=20261119235416.1681888-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.