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
Subject: Re: CVE-2021-47090: mm/hwpoison: clear MF_COUNT_INCREASED before retrying get_any_page()
Date: Wed, 6 Mar 2024 08:41:01 +0000	[thread overview]
Message-ID: <2024030629-evoke-imply-db5c@gregkh> (raw)
In-Reply-To: <ZegkEqtGcC1p_7Xb@tiehlicka>

On Wed, Mar 06, 2024 at 09:06:42AM +0100, Michal Hocko wrote:
> If you insist this still qualifies as a vulnaribility/weakness fix then
> I would propose a new category pig-with-a-lipstick-CVE.

We don't get to pick "categories" for CVEs, that's what other people do,
and I wish them the best of luck!  :)

thanks,

greg k-h

      parent reply	other threads:[~2024-03-06  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024030413-CVE-2021-47090-a429@gregkh>
2024-03-05 18:45 ` CVE-2021-47090: mm/hwpoison: clear MF_COUNT_INCREASED before retrying get_any_page() Michal Hocko
2024-03-05 22:20   ` Greg Kroah-Hartman
2024-03-06  8:06     ` Michal Hocko
2024-03-06  8:40       ` Greg Kroah-Hartman
2024-03-06  8:41       ` Greg Kroah-Hartman [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=2024030629-evoke-imply-db5c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@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