linux-kernel - Re: [PATCH] x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YgO9kyM6C4HResiG@kroah.com>
Date:   Wed, 9 Feb 2022 14:11:47 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     luofei <luofei@...cloud.com>
Cc:     stable@...r.kernel.org, tony.luck@...el.com, bp@...en8.de,
        tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
        x86@...nel.org, linux-edac@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages
 check condition

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@...cloud.com>
> Cc: stable@...r.kernel.org #v4.14.x
> Cc: stable@...r.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