All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: luofei <luofei@unicloud.com>
Cc: stable@vger.kernel.org, tony.luck@intel.com, bp@alien8.de,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition
Date: Wed, 9 Feb 2022 14:11:47 +0100	[thread overview]
Message-ID: <YgO9kyM6C4HResiG@kroah.com> (raw)
In-Reply-To: <20220208032028.852302-1-luofei@unicloud.com>

On Mon, Feb 07, 2022 at 10:20:28PM -0500, luofei wrote:
> [ Upstream commit fd0e786d9d09024f67bd71ec094b110237dc3840 ]
> 
> This commit solves the problem of unmap kernel 1:1 pages
> unconditionally, it appears in Linus's tree 4.16 and later
> versions, and is backported to 4.14.x and 4.15.x stable branches.
> 
> But the backported patch has its logic reversed when calling
> memory_failure() to determine whether it needs to unmap the
> kernel page. Only when memory_failure() returns successfully,
> the kernel page can be unmapped.
> 
> Signed-off-by: luofei <luofei@unicloud.com>
> Cc: stable@vger.kernel.org #v4.14.x
> Cc: stable@vger.kernel.org #v4.15.x
> ---
>  arch/x86/kernel/cpu/mcheck/mce.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, now queued up.

greg k-h

      reply	other threads:[~2022-02-09 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  3:20 [PATCH] x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition luofei
2022-02-09 13:11 ` 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=YgO9kyM6C4HResiG@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luofei@unicloud.com \
    --cc=mingo@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.