Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ronnie Sahlberg <rsahlberg@ciq.com>
Cc: stable@vger.kernel.org
Subject: Re: Candidates for stable v6.9..v6.10-rc3 NULL pointers
Date: Wed, 19 Jun 2024 13:58:34 +0200	[thread overview]
Message-ID: <2024061924-obedience-doorframe-12da@gregkh> (raw)
In-Reply-To: <CAK4epfyJJKm6kShw9Fa0dA=ns3CK8wjA4v236nRfubxfibnRFw@mail.gmail.com>

On Sat, Jun 15, 2024 at 07:28:30PM -0400, Ronnie Sahlberg wrote:
> Manually checked list of commits in upstream that mention NULL pointers and
> that reference that they fix a commit that is in linux-running-stable.
> 
> a9b9741854a9fe9df948
> c4ab9da85b9df3692f86
> c44711b78608c98a3e6b
> 0dcc53abf58d572d34c5

All already grabbed.

> 445c0b69c72903528fdf

Note, this one references a 6.10-rc1 commit, so it can't be included.
Don't know if you want to add that to your script to check.

> 97ab3e8eec0ce79d9e26

Same, 6.10-rc1.  And also, the check is wrong, that's not what this
commit does, you might want to read the commits :)

> 47558cbaa842c4561d08

Fixes 6.10-rc1

> 62cbabc6fd228e62daff

Fixes 6.10-rc1

> 02367f52901932674ff2

Welcome to my hell :(

This already is in the tree, as a totally different commit, and
backported properly, but the AMD developers seem to like to apply it to
different branches at the same time, AND give us no hints that they did
so.  Ugh, it's a mess and one reason I dread reviewing amdgpu driver
patches for stable these days...

thanks,

greg k-h

      reply	other threads:[~2024-06-19 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-15 23:28 Candidates for stable v6.9..v6.10-rc3 NULL pointers Ronnie Sahlberg
2024-06-19 11:58 ` Greg KH [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=2024061924-obedience-doorframe-12da@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