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 41F7DC4332F for ; Wed, 14 Dec 2022 08:52:19 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8A9DE8E0003; Wed, 14 Dec 2022 03:52:18 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 834D38E0002; Wed, 14 Dec 2022 03:52:18 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6FABA8E0003; Wed, 14 Dec 2022 03:52:18 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 5C4E88E0002 for ; Wed, 14 Dec 2022 03:52:18 -0500 (EST) Received: from smtpin27.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 27DFD140EDB for ; Wed, 14 Dec 2022 08:52:18 +0000 (UTC) X-FDA: 80240295156.27.CC92CEE Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf20.hostedemail.com (Postfix) with ESMTP id A1DBF1C0002 for ; Wed, 14 Dec 2022 08:52:16 +0000 (UTC) Authentication-Results: imf20.hostedemail.com; dkim=pass header.d=linuxfoundation.org header.s=korg header.b=0drlkZO2; spf=pass (imf20.hostedemail.com: domain of gregkh@linuxfoundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=gregkh@linuxfoundation.org; dmarc=pass (policy=none) header.from=linuxfoundation.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1671007936; 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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=TaKoUOeTGRwlzCtidKIq7LbHam8H49FcW68eZiX44h0=; b=0+L5q1j6kOcV5iZVzx8vT0z3o9JQNq8QA7nu87O8AILR0WdSBFaSCiFvY09RO2wMtiSdIg tdm2VWqLCTxJgmAKnQR0898qqqFr5OjrrozSjx4UWcaP/TDDI7J7zEUqwA93myxZJHDOxi 1B9RrQSuMe1+UhI9RQ65KsFjxI7HxO0= ARC-Authentication-Results: i=1; imf20.hostedemail.com; dkim=pass header.d=linuxfoundation.org header.s=korg header.b=0drlkZO2; spf=pass (imf20.hostedemail.com: domain of gregkh@linuxfoundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=gregkh@linuxfoundation.org; dmarc=pass (policy=none) header.from=linuxfoundation.org ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1671007936; a=rsa-sha256; cv=none; b=SK5lmDVcAPmLAdMwc+y/X6Fs33zggMVo+posym8c42Q0JwVr1riBw6cfnIHdGU1eM9+NAR dpLXCuk7gd2zI3limlZWB373KAv2uqTmBtLO4Fo4J09sFhT56UAm4Q3tBP055JfJpygNg0 2v7gaJw6FRzmVI8v14ndK3vow8sFnEM= Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 62B1461842; Wed, 14 Dec 2022 08:52:15 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 74295C433D2; Wed, 14 Dec 2022 08:52:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1671007934; bh=a44KHZV5ozazTqhTJY1VPwLhc0YsMskNoT1I+bEyLx8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=0drlkZO2dW/NQunugXLcGkykNhfwnToCPByJr8ieqBWd/49CA3ipjlx+DoCumkUuU UfpjxLijkaSKkFYKV2i/zmb1otKoGJ4PMZnNYnOQaqJRWpEmMfPAqx5s13403PlZJ9 JJomjyPWrCq7GqbRSjKLQaqRYaxxK3gvOEPhG3cs= Date: Wed, 14 Dec 2022 09:52:11 +0100 From: Greg KH To: mawupeng Cc: naoya.horiguchi@nec.com, catalin.marinas@arm.com, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [Qestion] UCE on pud-sized hugepage lead to kernel panic on lts5.10 Message-ID: References: <2b4d03bc-2b6e-45b0-655a-58b66672187e@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2b4d03bc-2b6e-45b0-655a-58b66672187e@huawei.com> X-Stat-Signature: i4tnikoi6o9wgjr7fuqxd87iexafd9gm X-Rspam-User: X-Rspamd-Queue-Id: A1DBF1C0002 X-Rspamd-Server: rspam06 X-HE-Tag: 1671007936-445643 X-HE-Meta: U2FsdGVkX19zrWQ9BFxHmtwK7GoaUDe1RL/APjlb/w3o0RVVJo/BTt/1uJnhuZVovmfHKMV0wCbCym3ylUJZi1lfaRw+HSDoddcB5rOjzx33zY43S5jirkgbskd9d3JP+zSpzjmcGYnYDrSJju5lkD/jSyGPj9IciK0dwS3zTKlsBdZhAhM0OZ/SsyDutEv7hvVjWv3Qj+lF4nn/LSihH1b6EYDrmA6YYimcW5/swOsi2JwS4VGgkif3/9ZexfDCUVbqf7u+8swN1h8iCpaRjcgB48klTCTLOM6g30xbhqulVn9Xsq9mZb7R5GtdF/tZCaoqn18S82CsWaDxtUSMr6lUWAmb1OZE64wCLydhd1j6xRoVO3WPDL5+yqxr3icB11AXObpBo2lE/lJ5OdWwhL6IcuYK3vfQslinRe3cXzVIeyXtEOhx2oaaQBiZuDML0L7Muxw5cjn2jDGXBHI2LnbdCnsTHDP9oTPFrG/g50+Owbix+r7yijK/8DKxNE0Xruu9tt0y0CSfsH5KQI5kW4kjq2sSh6zHpC9Vl9yQTUnFS7irgK+dpbNc/dBGGt6fWbZ/sOmCBJbFCXzNF10SWOCHxZgZ+qy8NQ9Ji7HOA0xO+qDVZ+TFPsyLCUWZn1/UFtND+Obv5NqgGA/J9NHWE5/tx0oB6kPQzwInRdLgD3076dDUt0J4ya4/gxgddjpEvHtCp2d7RbuprrIaHuvFvuXiB46fGW15vQ2FBxYlFNQmiZOvpKqIpw60U0dJqGupa45YdL0JpFQH4X/V/5uUoIO9bLF5cbnt1+GJTx7T/3kqvElr79ynaWDZtr7H1qMG+Ej6TtuoRY4NOVzZ/NZPnc3JjyVVCvSOhxhGUfGbL8sbyXqmsITierzNdq2bE/5ppNGi+9kj4uqrOq2vz4gH9WnBXfoqlxDxmN/ESKkP7QFHLjEdvrRXnVPMGIjadFNtzJnazF9RFLlO0ZykmZy c9oW9V8s teEITnCZsjegbkWs= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000001, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, Dec 14, 2022 at 09:33:10AM +0800, mawupeng wrote: > On current arm64 stable 5.10(v5.10.158). If a UCE happnes pud-sized > hugepage, kernel will panic since current memory failure can not handle > this kind of memory failure since commit 31286a8484a8 ("mm: hwpoison: > disable memory error handling on 1GB hugepage") > > The latest kernel(v6.0) can handle this UCE since commit 6f4614886baa ("mm, > hwpoison: enable memory error handling on 1GB hugepage"). We are trying to > backport this patchset to stable 5.10, however too many other patches > should be backport since there are huge difference between 5.10 and 6.0. > The full patch list will be shown at the end of this mail. > > We do not think backport all of these patches is doable for stable 5.10. Is > there any better way to fix this problem. Please just upgrade to 6.0 (or 6.1 as 6.0 will be end-of-life in a week or so). That is the simplest and easiest way to resolve the issue, right? Or what about 5.15.y? thanks, greg k-h