From patchwork Wed Apr 6 09:13:04 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Tong Tiangen X-Patchwork-Id: 12802716 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8EC0CC433EF for ; Wed, 6 Apr 2022 08:54:47 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 206516B0072; Wed, 6 Apr 2022 04:54:37 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1B62E6B0074; Wed, 6 Apr 2022 04:54:37 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 07F5F6B0075; Wed, 6 Apr 2022 04:54:37 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.a.hostedemail.com [64.99.140.24]) by kanga.kvack.org (Postfix) with ESMTP id EF5CE6B0072 for ; Wed, 6 Apr 2022 04:54:36 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay12.hostedemail.com (Postfix) with ESMTP id C588D121A6F for ; Wed, 6 Apr 2022 08:54:26 +0000 (UTC) X-FDA: 79325842932.11.75E19EE Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by imf06.hostedemail.com (Postfix) with ESMTP id D855A180011 for ; Wed, 6 Apr 2022 08:54:25 +0000 (UTC) Received: from kwepemi500002.china.huawei.com (unknown [172.30.72.56]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4KYJGD3StlzdZY5; Wed, 6 Apr 2022 16:53:56 +0800 (CST) Received: from kwepemm600017.china.huawei.com (7.193.23.234) by kwepemi500002.china.huawei.com (7.221.188.171) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 6 Apr 2022 16:54:23 +0800 Received: from localhost.localdomain (10.175.112.125) by kwepemm600017.china.huawei.com (7.193.23.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Wed, 6 Apr 2022 16:54:22 +0800 From: Tong Tiangen To: Andrew Morton , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , Catalin Marinas , Will Deacon , Alexander Viro , , "H. Peter Anvin" CC: , , , Tong Tiangen Subject: [RFC PATCH -next V2 0/7]arm64: add machine check safe support Date: Wed, 6 Apr 2022 09:13:04 +0000 Message-ID: <20220406091311.3354723-1-tongtiangen@huawei.com> X-Mailer: git-send-email 2.18.0.huawei.25 MIME-Version: 1.0 X-Originating-IP: [10.175.112.125] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To kwepemm600017.china.huawei.com (7.193.23.234) X-CFilter-Loop: Reflected X-Rspamd-Server: rspam09 X-Rspam-User: X-Stat-Signature: r6pjkemysgcd7gsrmu116wz8g3szdgwx Authentication-Results: imf06.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf06.hostedemail.com: domain of tongtiangen@huawei.com designates 45.249.212.187 as permitted sender) smtp.mailfrom=tongtiangen@huawei.com X-Rspamd-Queue-Id: D855A180011 X-HE-Tag: 1649235265-20279 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: This patchset is based on[1]. With the increase of memory capacity and density, the probability of memory error increases. The increasing size and density of server RAM in the data center and cloud have shown increased uncorrectable memory errors. Currently, the kernel has a mechanism to recover from hardware memory errors. This patchset provides an new recovery mechanism. For ARM64, the hardware error handling is do_sea() which divided into two cases: 1. The user state consumed the memory errors, the solution is kill th user process and isolate the error page. 2. The kernel state consumed the memory errors, the solution is panic. For kernelspace, Undifferentiated panic maybe not the optimal choice, it can be handled better. This patchset deals with four sscenarios of hardware memory error consumed in kernelspace: 1. copy_from_user. 2. get_user. 3. cow(copy on write). 4. pagecache reading. These four scenarios have similarities. Although the error is consumed in the kernel state, but the consumed data belongs to the user state. The processing scheme is based on CONFIG_ARCH_HAS_COPY_MC and uses the process killing plus isolate error page to replace kernel panic. [1]https://lore.kernel.org/lkml/20220323033705.3966643-1-tongtiangen@huawei.com/ Since V2: 1.Consistent with PPC/x86, Using CONFIG_ARCH_HAS_COPY_MC instead of ARM64_UCE_KERNEL_RECOVERY. 2.Add two new scenarios, cow and pagecache reading. 3.Fix two small bug(the first two patch). Tong Tiangen (7): x86: fix copy_mc_to_user compile error arm64: fix page_address return value in copy_highpage arm64: add support for machine check error safe arm64: add copy_from_user to machine check safe arm64: add get_user to machine check safe arm64: add cow to machine check safe arm64: add pagecache reading to machine check safe arch/arm64/Kconfig | 1 + arch/arm64/include/asm/asm-extable.h | 25 +++++++ arch/arm64/include/asm/asm-uaccess.h | 16 +++++ arch/arm64/include/asm/esr.h | 5 ++ arch/arm64/include/asm/extable.h | 2 +- arch/arm64/include/asm/page.h | 10 +++ arch/arm64/include/asm/uaccess.h | 17 ++++- arch/arm64/kernel/probes/kprobes.c | 2 +- arch/arm64/lib/Makefile | 2 + arch/arm64/lib/copy_from_user.S | 11 ++-- arch/arm64/lib/copy_page_mc.S | 98 ++++++++++++++++++++++++++++ arch/arm64/lib/copy_to_user_mc.S | 78 ++++++++++++++++++++++ arch/arm64/mm/copypage.c | 36 ++++++++-- arch/arm64/mm/extable.c | 21 +++++- arch/arm64/mm/fault.c | 30 ++++++++- arch/x86/include/asm/uaccess.h | 1 + include/linux/highmem.h | 8 +++ include/linux/uaccess.h | 8 +++ include/linux/uio.h | 9 ++- lib/iov_iter.c | 85 +++++++++++++++++++----- mm/memory.c | 2 +- 21 files changed, 432 insertions(+), 35 deletions(-) create mode 100644 arch/arm64/lib/copy_page_mc.S create mode 100644 arch/arm64/lib/copy_to_user_mc.S