linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
	"Andrew Morton" <akpm@linux-foundation.org>
Cc: Xu Yu <xuyu@linux.alibaba.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"osalvador@suse.de" <osalvador@suse.de>
Subject: Re: [PATCH v2] mm/memory-failure.c: skip huge_zero_page in memory_failure()
Date: Sat, 16 Apr 2022 09:47:35 +0800	[thread overview]
Message-ID: <c738cf74-f172-57dc-c6c4-3d703d33e3be@huawei.com> (raw)
In-Reply-To: <20220415061645.GA3364289@hori.linux.bs1.fc.nec.co.jp>

On 2022/4/15 14:16, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Tue, Apr 12, 2022 at 01:01:02PM -0700, Andrew Morton wrote:
>> On Tue, 12 Apr 2022 23:11:01 +0800 Xu Yu <xuyu@linux.alibaba.com> wrote:
>>
>>> Kernel panic when injecting memory_failure for the global huge_zero_page,
>>> when CONFIG_DEBUG_VM is enabled, as follows.
>>>
>>> ...
>>>
>>>
>>> Reported-by: Abaci <abaci@linux.alibaba.com>
>>> Suggested-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
>>> Cc: Miaohe Lin <linmiaohe@huawei.com>
>>> Cc: Oscar Salvador <osalvador@suse.de>
>>> Signed-off-by: Xu Yu <xuyu@linux.alibaba.com>

LGTM. Thanks.

Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>

> 
> Thank you for the patch.
> 
> Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
> 
>>
>> Thanks, I added a cc:stable to this.
>>
>> If anyone could suggest a suitable Fixes:, that would help the -stable
>> people.
> 
> The problem was existing from the origin of memory_failure, so the following
> Fixes: tag looks fine to me.
> 
> Fixes: 6a46079cf57a ("HWPOISON: The high level memory error handler in the VM v7")

Thanks for your Fixes tag. But huge zero page is not even introduced in that commit.
So maybe Fixes: 4a6c1297268c ("thp: huge zero page: basic preparation") which introduced
huge zero page will be more suitable?

Thanks!

> 
> Thanks,
> Naoya Horiguchi
> 


  reply	other threads:[~2022-04-16  1:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 15:11 Xu Yu
2022-04-12 20:01 ` Andrew Morton
2022-04-15  6:16   ` HORIGUCHI NAOYA(堀口 直也)
2022-04-16  1:47     ` Miaohe Lin [this message]
2022-04-20 23:38 ` Yang Shi
2022-04-21  9:03   ` David Hildenbrand
2022-04-21 11:18     ` Anshuman Khandual
2022-04-21 17:53     ` Yang Shi
2022-04-22  1:00       ` HORIGUCHI NAOYA(堀口 直也)
2022-04-22  3:27       ` Yu Xu
2022-04-22 16:03         ` Yang Shi
2022-04-22 17:37           ` Yu Xu
2022-04-22 17:58             ` Yang Shi
2022-04-21 11:15 ` Anshuman Khandual
2022-04-23  3:16 ` Yu Xu
2022-04-25 14:16   ` HORIGUCHI NAOYA(堀口 直也)
2022-04-26  6:48     ` Anshuman Khandual
2022-04-26  6:58       ` HORIGUCHI NAOYA(堀口 直也)
2022-05-02  5:59         ` Anshuman Khandual

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=c738cf74-f172-57dc-c6c4-3d703d33e3be@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@nec.com \
    --cc=osalvador@suse.de \
    --cc=xuyu@linux.alibaba.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