linux-kernel - [RFC PATCH v1 0/2] ACPI: APEI: Make synchronization errors call

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

Message-ID: <20221207093935.1972530-1-lvying6@huawei.com>
Date:   Wed, 7 Dec 2022 17:39:33 +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>,
        <lvying6@...wei.com>, <linux-acpi@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>
Subject: [RFC PATCH v1 0/2] ACPI: APEI: Make synchronization errors call

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