From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Yu Xu <xuyu@linux.alibaba.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Yang Shi <shy828301@gmail.com>,
David Hildenbrand <david@redhat.com>,
"anshuman.khandual@arm.com" <anshuman.khandual@arm.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"osalvador@suse.de" <osalvador@suse.de>
Subject: Re: [PATCH v2] mm/memory-failure.c: skip huge_zero_page in memory_failure()
Date: Mon, 25 Apr 2022 14:16:50 +0000 [thread overview]
Message-ID: <20220425141649.GB3767079@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <8e1a882c-8568-57f2-216a-703f220e0e3f@linux.alibaba.com>
On Sat, Apr 23, 2022 at 11:16:20AM +0800, Yu Xu wrote:
> For this patch v2,
>
> Yang, David, Anshuman and Naoya all agree to fix the bug in
> split_huge_page_to_list(), i.e., to replace the BUG to
> WARN + returning -EBUSY for huge_zero_page.
>
> However, this patch v2 has just been merged into linux mainline.
> Sorry for that I didn't hurry up.
>
> So now, should we continue sending v3, or should we end this
> thread, and start a successive patch for optimization?
No problem, you can start a new thread for additional patches.
Maybe it's better to have separate patches (starting with one
reverting v2 and then one doing v3).
Thanks,
Naoya Horiguchi
next prev parent reply other threads:[~2022-04-25 14:16 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
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(堀口 直也) [this message]
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=20220425141649.GB3767079@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--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