All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Sasha Levin <sashal@kernel.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,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04)
Date: Fri, 20 Nov 2026 15:39:10 -0500	[thread overview]
Message-ID: <2026-11-20-1-daily-reply-0021@kernel.org> (raw)
In-Reply-To: <2026112048-paper-radiance-199e@gregkh>

> > >> Commit: 3adf7ae18bf4
> > >> Date: Apr 18
> > >> Fix: Partial mremap of the ring
[...]
> Great, then someone should have tagged these for stable inclusion, or
> let us know after the fact :(

Queued 3adf7ae18bf4 ("fs: aio: reject partial mremap to avoid
Null-pointer-dereference error") for 6.18, 6.12, 6.6, 6.1, 5.15 and 5.10.

c03ce4173c7b ("fs: aio: set VMA_DONTCOPY_BIT in mmap to fix
NULL-pointer-dereference error") isn't needed for the crash there: d53b5aa5cfae
("aio: fix NULL deref when a fault races ring truncation") is already queued on
all of those trees, and its ->read_folio returning -EIO closes the fork route
too, so c03ce4173c7b would only change fork() behaviour.

-- 
Thanks,
Sasha

      reply	other threads:[~2026-11-20 20:39 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
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 [this message]

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=2026-11-20-1-daily-reply-0021@kernel.org \
    --to=sashal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=dev@rebasedinc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=io-uring@vger.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 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.