Linux io-uring development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.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
Subject: Re: io_uring/eventfd: registered eventfd signals only once after the cd305ee3633a backport (6.18.y, 6.12.y, Ubuntu 26.04)
Date: Tue, 17 Nov 2026 08:42:31 +0100	[thread overview]
Message-ID: <2026111722-unfocused-ride-065c@gregkh> (raw)
In-Reply-To: <07947062-2974-4630-90db-1556e25b50bb@kernel.dk>

On Mon, Nov 16, 2026 at 07:21:38PM -0700, Jens Axboe wrote:
> On 11/16/26 2:52 AM, Greg Kroah-Hartman wrote:
> > On Sat, Nov 14, 2026 at 11:12:40AM -0700, Jens Axboe wrote:
> >> On 11/14/26 10:42 AM, Sasha Levin wrote:
> >>> On 2026-11-13, dev@rebasedinc.com wrote:
> >>>> If this is correct, a backport of 04fe9aeb4f3c to 6.18.y and 6.12.y looks like the right fix; it keeps the CVE-2026-80920 fix in place.
> >>>
> >>> Queued for 6.18 and 6.12, thanks.
> >>
> >> Yet another bs CVE - Greg, please invalidate this one too, it's NOT CVE material.
> >> Getting a little tired of chasing these.
> > 
> > Now rejected, sorry about that.
> 
> Not sure how we improve on that, it's really annoying to catch these bogus
> ones after the fact?

How about we make the "rule" that we don't assign any kernel CVEs to
io_uring things unless you ask for us to?  We do this already with the
xen portions of the kernel, but it requires you to remember to ask us
for an id "manually" if you want one.

Or any other ideas?

thanks,

greg k-h

  reply	other threads:[~2026-11-17  7:42 UTC|newest]

Thread overview: 12+ 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 [this message]
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

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=2026111722-unfocused-ride-065c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=dev@rebasedinc.com \
    --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