Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Lv Ying <lvying6@huawei.com>
To:     <rafael@kernel.org>, <lenb@kernel.org>, <james.morse@arm.com>,
        <tony.luck@intel.com>, <bp@alien8.de>, <naoya.horiguchi@nec.com>,
        <linmiaohe@huawei.com>, <akpm@linux-foundation.org>,
        <xueshuai@linux.alibaba.com>, <ashish.kalra@amd.com>
CC:     <xiezhipeng1@huawei.com>, <wangkefeng.wang@huawei.com>,
        <xiexiuqi@huawei.com>, <tanxiaofei@huawei.com>,
        <lvying6@huawei.com>, <linux-acpi@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: [RFC PATCH v1 0/2] ACPI: APEI: Make synchronization errors call
Date:   Wed, 7 Dec 2022 17:39:33 +0800
Message-ID: <20221207093935.1972530-1-lvying6@huawei.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Content-Type:   text/plain; charset=US-ASCII
Precedence: bulk

Changes RFC PATCH v1 -> RFC
============================
1. add TODO to explain current there is no good way to distinguish
ghes_proc_in_irq is called by synchronous or asynchronous error, so keep
consistent with the current implementation
2. filter out -EHWPOISON and -EOPNOTSUPP just like kill_me_maybe() 

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 | 36 ++++++++++++++++++++------------
 mm/memory-failure.c      | 45 ++++++++++++++++++++++++++++------------
 2 files changed, 55 insertions(+), 26 deletions(-)

-- 
2.36.1