From: Anshuman Khandual <anshuman.khandual@arm.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"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>,
"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: Tue, 26 Apr 2022 12:18:39 +0530 [thread overview]
Message-ID: <4a004118-ff5a-ca2e-e707-5886c41045b5@arm.com> (raw)
In-Reply-To: <20220425141649.GB3767079@hori.linux.bs1.fc.nec.co.jp>
On 4/25/22 19:46, HORIGUCHI NAOYA(堀口 直也) wrote:
> 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).
May be also pull in the following patch which adds MF_MSG_HUGE_ZERO
in the same series ?
https://lore.kernel.org/linux-mm/20220425080306.1771480-1-anshuman.khandual@arm.com/
next prev parent reply other threads:[~2022-04-26 6: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
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 [this message]
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=4a004118-ff5a-ca2e-e707-5886c41045b5@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--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