public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michal Hocko <mhocko@suse.com>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
	linux-cve-announce@vger.kernel.org
Subject: Re: CVE-2024-35906: drm/amd/display: Send DTBCLK disable message on first commit
Date: Tue, 21 May 2024 16:39:51 +0200	[thread overview]
Message-ID: <2024052136-cubbyhole-ecologist-5b68@gregkh> (raw)
In-Reply-To: <ZkxbObACcnUMZ3LA@tiehlicka>

On Tue, May 21, 2024 at 10:28:41AM +0200, Michal Hocko wrote:
> CVE-2024-35881 to revert f341055b10bd ("drm/amd/display: Send DTBCLK
> disable message on first commit") by 3a6a32b31a11 ("Revert
> "drm/amd/display: Send DTBCLK disable message on first commit"") has
> been filed as well.
> 
> Is this really intentional? Should both be rejected?

I don't think so as we had releases with the original commit in it,
which was buggy so then the second one was needed.  So if you only took
the first fix, you have a problem, and need the second one.  If you take
both, all is good.  If you took neither, also all is good.  So be safe
and take both :)

thanks,

greg k-h

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024051954-CVE-2024-35906-1c6f@gregkh>
2024-05-21  8:28 ` CVE-2024-35906: drm/amd/display: Send DTBCLK disable message on first commit Michal Hocko
2024-05-21 14:39   ` Greg Kroah-Hartman [this message]
2024-05-21 16:51     ` Michal Hocko
2024-05-21 17:03       ` Greg Kroah-Hartman
2024-05-21 17:56         ` Michal Hocko
2024-05-22  3:57           ` Greg Kroah-Hartman
2024-05-23  8:26             ` Michal Hocko
2024-05-23 13:49               ` Greg Kroah-Hartman
2024-05-24 10:10                 ` Michal Hocko
2024-05-24 11:47                   ` Greg Kroah-Hartman
2024-05-24 14:02                     ` Michal Hocko
2024-05-24 15:22                       ` Greg Kroah-Hartman
2024-05-24 15:59                         ` Michal Hocko

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=2024052136-cubbyhole-ecologist-5b68@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    /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