public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ronnie Sahlberg <rsahlberg@ciq.com>
Cc: stable@vger.kernel.org
Subject: Re: commits for stable 2024-05-11
Date: Sun, 12 May 2024 13:21:30 +0100	[thread overview]
Message-ID: <2024051256-joyfully-unframed-dd66@gregkh> (raw)
In-Reply-To: <CAK4epfysW+3vA9BM94iQVUaH3k-DNoyHAwUeYaCeGdbZ3dOyQQ@mail.gmail.com>

On Sat, May 11, 2024 at 09:13:25PM -0400, Ronnie Sahlberg wrote:
> Please find attached a report generated by keyword matching commits
> from upstream that may be suitable for stable and probably as CVEs as
> well.

This is great, thanks for looking into this and sending this out!

> I exclude commits that are already tagged with CC stable in upstream
> and also commits already in
> stable/linux-rolling-stable.

I took a very short look, and just picked one commit at random on the
bottom of the list:
	cf2df0080bd59cb97a15

And it's included in 6.8.2 already, as commit 9c68e3497b61 ("wifi:
ath11k: fix a possible dead lock caused by ab->base_lock").

So is your tooling working?

Also, give us a chance to catch up on commits that are in Linus's tree,
but not in a -rc release, which you list a few at the top of the list.
We aren't allowed to apply them until after they hit a -rc release.

thanks,

greg k-h

  reply	other threads:[~2024-05-12 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12  1:13 commits for stable 2024-05-11 Ronnie Sahlberg
2024-05-12 12:21 ` Greg KH [this message]
2024-05-12 22:35   ` Ronnie Sahlberg
2024-05-14 12:11     ` Greg KH
2024-05-14 12:13     ` Greg KH

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=2024051256-joyfully-unframed-dd66@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=rsahlberg@ciq.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox