linux-kernel - Re: [PATCH] x86/mce: Always call kill_me_maybe() to handle memory failure in user mode

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: <Ye51rSZgBhpl4lzD@zn.tnic>
Date:   Mon, 24 Jan 2022 10:47:25 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     luofei <luofei@...cloud.com>
Cc:     tony.luck@...el.com, tglx@...utronix.de, mingo@...hat.com,
        dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
        linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/mce: Always call kill_me_maybe() to handle memory
 failure in user mode

On Mon, Jan 24, 2022 at 03:15:01AM -0500, luofei wrote:
> Just killing the current process is not enough, it is necessory
> to offload the faulty page.
> 
> In the virtualization scenario, qemu does not set MCG_STATUS_RIPV by
> default.

Yes, we've had this before. Fix qemu.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette