From mboxrd@z Thu Jan 1 00:00:00 1970 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 3D761E77188 for ; Thu, 19 Dec 2024 01:44:13 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C1C526B0082; Wed, 18 Dec 2024 20:44:12 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id BCB696B0083; Wed, 18 Dec 2024 20:44:12 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A6BE46B0085; Wed, 18 Dec 2024 20:44:12 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 881C66B0082 for ; Wed, 18 Dec 2024 20:44:12 -0500 (EST) Received: from smtpin17.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 0CA51C11C9 for ; Thu, 19 Dec 2024 01:44:12 +0000 (UTC) X-FDA: 82910010834.17.A29E4BB Received: from out30-100.freemail.mail.aliyun.com (out30-100.freemail.mail.aliyun.com [115.124.30.100]) by imf21.hostedemail.com (Postfix) with ESMTP id E5D4D1C0018 for ; Thu, 19 Dec 2024 01:43:06 +0000 (UTC) Authentication-Results: imf21.hostedemail.com; dkim=pass header.d=linux.alibaba.com header.s=default header.b=aCRC4JkE; spf=pass (imf21.hostedemail.com: domain of xueshuai@linux.alibaba.com designates 115.124.30.100 as permitted sender) smtp.mailfrom=xueshuai@linux.alibaba.com; dmarc=pass (policy=none) header.from=linux.alibaba.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1734572625; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=LsMRam799y1BeBH01GzJpZAfi+0+C0lyLFmFJu0j0GQ=; b=q7rsHlShl7XSb4AHvKq/h0JZR/U78XQniWrgW2FfP6WpD0bp7XaxiCeAZcjL8Byl7vm97J kOAEzCnO04cb54Jttt2wfUSoZnetflR3qLtu929C0Xv7De9sobnAXp+o3/dfqSWT+EVP36 6KG21BIQGRladdBSZ3wf2veFhukioH8= ARC-Authentication-Results: i=1; imf21.hostedemail.com; dkim=pass header.d=linux.alibaba.com header.s=default header.b=aCRC4JkE; spf=pass (imf21.hostedemail.com: domain of xueshuai@linux.alibaba.com designates 115.124.30.100 as permitted sender) smtp.mailfrom=xueshuai@linux.alibaba.com; dmarc=pass (policy=none) header.from=linux.alibaba.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1734572625; a=rsa-sha256; cv=none; b=0xSPQK7QiAfG/ZjIIJCIKfRII1+E5q6NlBuxmBfv5qvDNnpzusyWsMExGO4fzJm2lFn0hz kzj/Wkv3wdfbzI5XVSaLgDXfgYxccQGNAmPdMKf9NWlxyxoMqgYGABiR4bY9KUY59K84IK tTKmt8f+ywVYg6us+T1OhzOQOLyD14k= DKIM-Signature:v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.alibaba.com; s=default; t=1734572645; h=Message-ID:Date:MIME-Version:Subject:To:From:Content-Type; bh=LsMRam799y1BeBH01GzJpZAfi+0+C0lyLFmFJu0j0GQ=; b=aCRC4JkEajWHQwHxXoWPVfw1/MSoLSTfQEGaYaiFNigymQx1tIA1B+pfw1cUM9t9UZPd+VvapQ55GcRFnYH9JF0LMi0G2U9j3lqn/IMyo+q8yzM4FiGpjhfmA5AsANyWdSGeAsVA8uUFg9yWIz/h8DgSqo5jovpLqER/qalq738= Received: from 30.246.161.240(mailfrom:xueshuai@linux.alibaba.com fp:SMTPD_---0WLoNiHx_1734572640 cluster:ay36) by smtp.aliyun-inc.com; Thu, 19 Dec 2024 09:44:02 +0800 Message-ID: Date: Thu, 19 Dec 2024 09:43:59 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v17 3/3] ACPI: APEI: handle synchronous exceptions in task work To: Yazen Ghannam Cc: mark.rutland@arm.com, catalin.marinas@arm.com, mingo@redhat.com, robin.murphy@arm.com, Jonathan.Cameron@huawei.com, bp@alien8.de, rafael@kernel.org, linux-arm-kernel@lists.infradead.org, wangkefeng.wang@huawei.com, tanxiaofei@huawei.com, mawupeng1@huawei.com, tony.luck@intel.com, linmiaohe@huawei.com, naoya.horiguchi@nec.com, james.morse@arm.com, tongtiangen@huawei.com, gregkh@linuxfoundation.org, will@kernel.org, jarkko@kernel.org, linux-acpi@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, linux-edac@vger.kernel.org, x86@kernel.org, justin.he@arm.com, ardb@kernel.org, ying.huang@intel.com, ashish.kalra@amd.com, baolin.wang@linux.alibaba.com, tglx@linutronix.de, dave.hansen@linux.intel.com, lenb@kernel.org, hpa@zytor.com, robert.moore@intel.com, lvying6@huawei.com, xiexiuqi@huawei.com, zhuo.song@linux.alibaba.com References: <20241202030527.20586-1-xueshuai@linux.alibaba.com> <20241202030527.20586-4-xueshuai@linux.alibaba.com> <20241218165331.GF1155365@yaz-khff2.amd.com> From: Shuai Xue In-Reply-To: <20241218165331.GF1155365@yaz-khff2.amd.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: E5D4D1C0018 X-Rspamd-Server: rspam12 X-Stat-Signature: b69g6ims6jr1dgpjc31kuu78kjds9aj7 X-Rspam-User: X-HE-Tag: 1734572586-262987 X-HE-Meta: U2FsdGVkX1/dPjjfKjufxjP2eh11/2pL2fltZAOQ/kk7xvpaV7Uy2gaV/DWjyPjFobu4y07ko+W1Ql89NsX9zEOt2jAqGP0XjDnfRXSUJReBGqxhbNBDNwTb8mv5Np8nmgFt+KdKq1cV0ZNHeMxT9fRukATzr3Ko5NVY2HGJ+Ph7RNAn7QcMnNvavGAi4YIFsmJ0vynsntsxSxw2Fv42g+5kI8/FC6tmVWrh6khfyWTSLBPw0T9qjejzJv2+sogLpTF+9O7uyt4ikoINzo7nomvChBit8oBlvqQdSh2+jdxTfnC6/6FTozRNU0XXHgPpAVolJ/Gm7r4AnSQfOgwfF4hyu+xDVyAJY4govRCXnP1Q/Gc7rNkHF772xwvpJ5qo98jrQlZjKAY5qDtXNHDR80gHLK3BLVPMcF0nuWtJ5yrMmQy+1JVG0X1Uo1ZO0CjjfzS8qHlD/1eJEwkXAeCQLG9Kd8IbYSvmx7fo7YbRyiNfyZSHc0lT3otRgvdeN86sY9aYDuM7TicE8K/6MOSU3HAZBM8xecnTVAxv/aLEs7eQBg7S3U//3IBgIwIfQzfw9iK1ERUwDc4POoiiSQZ6Qb6KZuhYxLrKwdvw+IZ93T47ZEcVsKdrJLQWFlfTMgD0woG+HfEwGMpAby7RcOqCUF3jYm9A6ZkF2+dIudJbEBFa3fSzyzVkWNqeX1wIWPnffvdHYej3Jf0Gx7576hvaSQHUxfp/qg9OpF+zLfF+GtjFoRVUG7qHDCiZkQYvv9mWWhDq1gK/A4UTgzcSXWNmTZN2KcPHxlOxzbPTnNDMy7ETJCJYUPxKPMZ5jYYDTdSGePKRrV6JO2aPfT5UZV8rODfD0OTggrxYJIP7baWma8cDdEreIYVrhoInR6fpNp62GbOuasAlgKEHdBKGQz4Sb+ERyGSGPDwZg8vJQaKtJZeNi1G/O+RwZFW1o5E8opivRkUE3uh0B7OHPLvWH9P Qkt4kINP FnVxyB34HpG/nRQtfo4TC9iVPBMsth0PMI8l1OvR8wFHY7yq9NNnvJWbd2EnRXRnF9uS48PEqxvkg7zS8OB2C0gVu4aGzEIX5+0dWbVzMwbTVtTGKy+BUk61BAYUNY3VqwZtvzrb6xnPU7xi46H4rL6GV2yQ+rD1cIC36keZ9+WBAfx5OKflPF5FzpddNFeWAkVNy9APxQTQUwOBwUXDtggqEGC6akCE8hyPjILDNfTELg3L8YYXBjV+y0pLnEtagQxzPVrb5bOzmaOyAIkbjiICAmGk1W/6nGPOhQWVRzk94q38REN4+uaInk/urMVSg1bfRsTyYKW92tCb1xSPUY5958/0PG0S+Uy9yP1wJp3ilRMVN5F4aAt0oGQ== 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: List-Subscribe: List-Unsubscribe: 在 2024/12/19 00:53, Yazen Ghannam 写道: > On Mon, Dec 02, 2024 at 11:05:27AM +0800, Shuai Xue wrote: >> The memory uncorrected error could be signaled by asynchronous interrupt >> (specifically, SPI in arm64 platform), e.g. when an error is detected by >> a background scrubber, or signaled by synchronous exception >> (specifically, data abort exception in arm64 platform), e.g. when a CPU >> tries to access a poisoned cache line. Currently, both synchronous and >> asynchronous error use memory_failure_queue() to schedule >> memory_failure() to exectute in a kworker context. >> >> As a result, when a user-space process is accessing a poisoned data, a >> data abort is taken and the memory_failure() is executed in the kworker >> context, memory_failure(): >> >> - will send wrong si_code by SIGBUS signal in early_kill mode, and >> - can not kill the user-space in some cases resulting a synchronous >> error infinite loop >> >> Issue 1: send wrong si_code in early_kill mode >> >> Since commit a70297d22132 ("ACPI: APEI: set memory failure flags as >> MF_ACTION_REQUIRED on synchronous events")', the flag MF_ACTION_REQUIRED >> could be used to determine whether a synchronous exception occurs on >> ARM64 platform. When a synchronous exception is detected, the kernel is >> expected to terminate the current process which has accessed poisoned >> page. This is done by sending a SIGBUS signal with an error code >> BUS_MCEERR_AR, indicating an action-required machine check error on >> read. >> >> However, when kill_proc() is called to terminate the processes who have >> the poisoned page mapped, it sends the incorrect SIGBUS error code >> BUS_MCEERR_AO because the context in which it operates is not the one >> where the error was triggered. >> >> To reproduce this problem: >> >> #sysctl -w vm.memory_failure_early_kill=1 >> vm.memory_failure_early_kill = 1 >> >> # STEP2: inject an UCE error and consume it to trigger a synchronous error >> #einj_mem_uc single >> 0: single vaddr = 0xffffb0d75400 paddr = 4092d55b400 >> injecting ... >> triggering ... >> signal 7 code 5 addr 0xffffb0d75000 >> page not present >> Test passed >> >> The si_code (code 5) from einj_mem_uc indicates that it is BUS_MCEERR_AO >> error and it is not the fact. >> >> After this patch: >> >> # STEP1: enable early kill mode >> #sysctl -w vm.memory_failure_early_kill=1 >> vm.memory_failure_early_kill = 1 >> # STEP2: inject an UCE error and consume it to trigger a synchronous error >> #einj_mem_uc single >> 0: single vaddr = 0xffffb0d75400 paddr = 4092d55b400 >> injecting ... >> triggering ... >> signal 7 code 4 addr 0xffffb0d75000 >> page not present >> Test passed >> >> The si_code (code 4) from einj_mem_uc indicates that it is a BUS_MCEERR_AR >> error as we expected. >> >> Issue 2: a synchronous error infinite loop >> >> If a user-space process, e.g. devmem, accesses a poisoned page for which >> the HWPoison flag is set, kill_accessing_process() is called to send >> SIGBUS to current processs with error info. Because the memory_failure() >> is executed in the kworker context, it will just do nothing but return >> EFAULT. So, devmem will access the posioned page and trigger an >> exception again, resulting in a synchronous error infinite loop. Such >> exception loop may cause platform firmware to exceed some threshold and >> reboot when Linux could have recovered from this error. >> >> To reproduce this problem: >> >> # STEP 1: inject an UCE error, and kernel will set HWPosion flag for related page >> #einj_mem_uc single >> 0: single vaddr = 0xffffb0d75400 paddr = 4092d55b400 >> injecting ... >> triggering ... >> signal 7 code 4 addr 0xffffb0d75000 >> page not present >> Test passed >> >> # STEP 2: access the same page and it will trigger a synchronous error infinite loop >> devmem 0x4092d55b400 >> >> To fix above two issues, queue memory_failure() as a task_work so that >> it runs in the context of the process that is actually consuming the >> poisoned data. >> >> Signed-off-by: Shuai Xue >> Tested-by: Ma Wupeng >> Reviewed-by: Kefeng Wang >> Reviewed-by: Xiaofei Tan >> Reviewed-by: Baolin Wang >> Reviewed-by: Jarkko Sakkinen >> Reviewed-by: Jonathan Cameron >> --- >> drivers/acpi/apei/ghes.c | 77 +++++++++++++++++++++++----------------- >> include/acpi/ghes.h | 3 -- >> include/linux/mm.h | 1 - >> mm/memory-failure.c | 13 ------- >> 4 files changed, 44 insertions(+), 50 deletions(-) >> >> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c >> index 106486bdfefc..70f2ee3ad1a8 100644 >> --- a/drivers/acpi/apei/ghes.c >> +++ b/drivers/acpi/apei/ghes.c >> @@ -467,28 +467,41 @@ static void ghes_clear_estatus(struct ghes *ghes, >> } >> >> /* > > The "kernel-doc" format needs an opening "/**". > >> - * Called as task_work before returning to user-space. >> - * Ensure any queued work has been done before we return to the context that >> - * triggered the notification. >> + * struct ghes_task_work - for synchronous RAS event >> + * >> + * @twork: callback_head for task work >> + * @pfn: page frame number of corrupted page >> + * @flags: work control flags >> + * >> + * Structure to pass task work to be handled before >> + * returning to user-space via task_work_add(). >> */ >> -static void ghes_kick_task_work(struct callback_head *head) >> +struct ghes_task_work { >> + struct callback_head twork; >> + u64 pfn; >> + int flags; >> +}; >> + >> +static void memory_failure_cb(struct callback_head *twork) >> { >> - struct acpi_hest_generic_status *estatus; >> - struct ghes_estatus_node *estatus_node; >> - u32 node_len; >> + struct ghes_task_work *twcb = container_of(twork, struct ghes_task_work, twork); >> + int ret; >> >> - estatus_node = container_of(head, struct ghes_estatus_node, task_work); >> - if (IS_ENABLED(CONFIG_ACPI_APEI_MEMORY_FAILURE)) >> - memory_failure_queue_kick(estatus_node->task_work_cpu); >> + ret = memory_failure(twcb->pfn, twcb->flags); >> + gen_pool_free(ghes_estatus_pool, (unsigned long)twcb, sizeof(*twcb)); >> >> - estatus = GHES_ESTATUS_FROM_NODE(estatus_node); >> - node_len = GHES_ESTATUS_NODE_LEN(cper_estatus_len(estatus)); >> - gen_pool_free(ghes_estatus_pool, (unsigned long)estatus_node, node_len); >> + if (!ret || ret == -EHWPOISON || ret == -EOPNOTSUPP) >> + return; >> + >> + pr_err("%#llx: Sending SIGBUS to %s:%d due to hardware memory corruption\n", >> + twcb->pfn, current->comm, task_pid_nr(current)); > > This is basically the same as the message in kill_proc(). Was there any > consideration to have a shared function? Maybe this could be a future > patch. Yep, I'd like to refactor in a future. > >> + force_sig(SIGBUS); >> } >> >> static bool ghes_do_memory_failure(u64 physical_addr, int flags) >> { >> unsigned long pfn; >> + struct ghes_task_work *twcb; > > Minor nit: A common preference I've seen is to order variable > declarations from longest->shortest line length. Will fix it if this patch set still misses the next merge window. > > But overall, looks okay to me. > > Reviewed-by: Yazen Ghannam > > Thanks, > Yazen Thanks for valuable comments. Best Regards, Shuai