Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sasha Levin <sashal@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
	Yufan Chen <yufan.chen@linux.dev>,
	dev@rebasedinc.com
Subject: Re: io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04)
Date: Thu, 19 Nov 2026 16:25:00 -0700	[thread overview]
Message-ID: <981f45d2-c38c-4ac1-893c-17ce3a8c3f0e@kernel.dk> (raw)
In-Reply-To: <20261119203921.972086-1-sashal@kernel.org>

On 11/19/26 1:39 PM, Sasha Levin wrote:
> On Thu, Nov 19, 2026 at 11:10:03AM -0700, Jens Axboe wrote:
>> But apparently nobody looks at aio?!
> 
> We do :) Here's what happened with each of them:

Good!

>> Commit: c03ce4173c7b
>> Date: Apr 13
>> Fix: Ring mapping inherited over fork
> 
>> Commit: 3adf7ae18bf4
>> Date: Apr 18
>> Fix: Partial mremap of the ring
> 
> Neither has a Fixes: or a stable tag, so they're not even in a stable tree.

Gotcha, that seems like a problem then for current maintained stable
kernels, where any user can crash it...

>> Commit: 398e3fa789aa
>> Date: Aug 13
>> Fix: eventfd/epoll recursion on poll
> 
>> Commit: d53b5aa5cfae
>> Date: Oct 29
>> Fix: Fault races ring truncation
> 
> Both shipped last week in 7.3.4, 6.18.63 and 6.12.117. My LLM review
> flagged both as CVE worthy. The 7.3.4 batch hasn't been assigned yet.

Makes sense.

>> Commit: b44341e39d85
>> Date: Oct 22
>> Fix: Request count overflow in ioctx_alloc()
>> CVE-worthy? Not in my opinion.
> 
> Agreed. No Fixes: or stable tag on this one either, and there hasn't been an
> AUTOSEL batch since it was merged, so it isn't in any stable tree.

And this one doesn't matter, imho.

>> Date: Oct 30
>> Fix: exit_aio() returns before complete()
> 
> I'm assuming this is ac4b449b39e6 ("aio: don't let exit_aio() return before
> complete() is done")? It has a stable tag but only went into v7.4-rc3, and it
> isn't in a stable release yet, so it hasn't come up for review.

OK, it was just late to the party then.

-- 
Jens Axboe

  reply	other threads:[~2026-11-19 23:25 UTC|newest]

Thread overview: 16+ 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-17 12:42         ` 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 [this message]
2026-11-20  5:17                     ` Greg Kroah-Hartman

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=981f45d2-c38c-4ac1-893c-17ce3a8c3f0e@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=dev@rebasedinc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=io-uring@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yufan.chen@linux.dev \
    /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