[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221205115111.131568-1-lvying6@huawei.com>
Date: Mon, 5 Dec 2022 19:51:09 +0800
From: Lv Ying <lvying6@...wei.com>
To: <rafael@...nel.org>, <lenb@...nel.org>, <james.morse@....com>,
<tony.luck@...el.com>, <bp@...en8.de>, <naoya.horiguchi@....com>,
<linmiaohe@...wei.com>, <akpm@...ux-foundation.org>,
<xueshuai@...ux.alibaba.com>, <ashish.kalra@....com>
CC: <xiezhipeng1@...wei.com>, <wangkefeng.wang@...wei.com>,
<xiexiuqi@...wei.com>, <tanxiaofei@...wei.com>,
<linux-acpi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>
Subject: [RFC 0/2] ACPI: APEI: Make synchronization errors call and
This patchset try to fix two problems:
- memory_failure() triggered by synchronization errors run in kernel
thread context
- ignore memory_failure() failure cause synchronous error infinite loop,
the platform firmware exceed some threshold and reboot
Lv Ying (2):
ACPI: APEI: Make memory_failure() triggered by synchronization errors
execute in the current context
ACPI: APEI: fix reboot caused by synchronous error loop because of
memory_failure() failed
drivers/acpi/apei/ghes.c | 27 ++++++++++++++-------------
mm/memory-failure.c | 38 ++++++++++++++++++++++++++------------
2 files changed, 40 insertions(+), 25 deletions(-)
--
2.33.0
Powered by blists - more mailing lists