linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: mawupeng <mawupeng1@huawei.com>
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
Date: Wed, 14 Dec 2022 09:52:11 +0100	[thread overview]
Message-ID: <Y5mOu7H7Adm2HytF@kroah.com> (raw)
In-Reply-To: <2b4d03bc-2b6e-45b0-655a-58b66672187e@huawei.com>

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


  reply	other threads:[~2022-12-14  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  1:33 mawupeng
2022-12-14  8:52 ` Greg KH [this message]
2022-12-14 17:04 ` Matthew Wilcox
2022-12-15  1:34   ` mawupeng
2022-12-15  1:01 ` HORIGUCHI NAOYA(堀口 直也)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y5mOu7H7Adm2HytF@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mawupeng1@huawei.com \
    --cc=naoya.horiguchi@nec.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox