linux-kernel - Re: [PATCH v10 2/4] ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2023121855-crimson-hamper-57ef@gregkh>
Date: Mon, 18 Dec 2023 07:54:03 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Shuai Xue <xueshuai@...ux.alibaba.com>
Cc: bp@...en8.de, rafael@...nel.org, wangkefeng.wang@...wei.com,
	tanxiaofei@...wei.com, mawupeng1@...wei.com, tony.luck@...el.com,
	linmiaohe@...wei.com, naoya.horiguchi@....com, james.morse@....com,
	will@...nel.org, jarkko@...nel.org, linux-acpi@...r.kernel.org,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, linux-edac@...r.kernel.org,
	acpica-devel@...ts.linuxfoundation.org, stable@...r.kernel.org,
	x86@...nel.org, justin.he@....com, ardb@...nel.org,
	ying.huang@...el.com, ashish.kalra@....com,
	baolin.wang@...ux.alibaba.com, tglx@...utronix.de, mingo@...hat.com,
	dave.hansen@...ux.intel.com, lenb@...nel.org, hpa@...or.com,
	robert.moore@...el.com, lvying6@...wei.com, xiexiuqi@...wei.com,
	zhuo.song@...ux.alibaba.com
Subject: Re: [PATCH v10 2/4] ACPI: APEI: send SIGBUS to current task if
 synchronous memory error not recovered

On Mon, Dec 18, 2023 at 02:45:19PM +0800, Shuai Xue wrote:
> Synchronous error was detected as a result of user-space process accessing
> a 2-bit uncorrected error. The CPU will take a synchronous error exception
> such as Synchronous External Abort (SEA) on Arm64. The kernel will queue a
> memory_failure() work which poisons the related page, unmaps the page, and
> then sends a SIGBUS to the process, so that a system wide panic can be
> avoided.
> 
> However, no memory_failure() work will be queued when abnormal synchronous
> errors occur. These errors can include situations such as invalid PA,
> unexpected severity, no memory failure config support, invalid GUID
> section, etc. In such case, the user-space process will trigger SEA again.
> This loop can potentially exceed the platform firmware threshold or even
> trigger a kernel hard lockup, leading to a system reboot.
> 
> Fix it by performing a force kill if no memory_failure() work is queued for synchronous errors.
> 
> Signed-off-by: Shuai Xue <xueshuai@...ux.alibaba.com>
> ---
>  drivers/acpi/apei/ghes.c | 9 +++++++++
>  1 file changed, 9 insertions(+)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>