From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
"shy828301@gmail.com" <shy828301@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] mm/memory-failure.c: make non-LRU movable pages unhandlable
Date: Sun, 13 Mar 2022 23:43:42 +0000 [thread overview]
Message-ID: <20220313234341.GC3010057@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20220312074613.4798-4-linmiaohe@huawei.com>
On Sat, Mar 12, 2022 at 03:46:13PM +0800, Miaohe Lin wrote:
> We can not really handle non-LRU movable pages in memory failure. Typically
> they are balloon, zsmalloc, etc. Assuming we run into a base (4K) non-LRU
> movable page, we could reach as far as identify_page_state(), it should not
> fall into any category except me_unknown. For the non-LRU compound movable
> pages, they could be taken for transhuge pages but it's unexpected to split
> non-LRU movable pages using split_huge_page_to_list in memory_failure. So
> we could just simply make non-LRU movable pages unhandlable to avoid these
> possible nasty cases.
>
> Suggested-by: Yang Shi <shy828301@gmail.com>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Looks good to me.
Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
next prev parent reply other threads:[~2022-03-13 23:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 7:46 [PATCH v2 0/3] A few fixup patches for memory failure Miaohe Lin
2022-03-12 7:46 ` [PATCH v2 1/3] mm/memory-failure.c: fix race with changing page compound again Miaohe Lin
2022-03-13 23:41 ` HORIGUCHI NAOYA(堀口 直也)
2022-03-14 1:51 ` Miaohe Lin
2022-03-14 18:20 ` Mike Kravetz
2022-03-15 14:19 ` Miaohe Lin
2022-03-15 18:19 ` Yang Shi
2022-03-16 8:18 ` Miaohe Lin
2022-03-16 8:30 ` HORIGUCHI NAOYA(堀口 直也)
2022-03-16 8:41 ` Miaohe Lin
2022-03-12 7:46 ` [PATCH v2 2/3] mm/memory-failure.c: avoid calling invalidate_inode_page() with unexpected pages Miaohe Lin
2022-03-13 23:41 ` HORIGUCHI NAOYA(堀口 直也)
2022-03-14 1:58 ` Miaohe Lin
2022-03-14 2:50 ` HORIGUCHI NAOYA(堀口 直也)
2022-03-14 2:59 ` Miaohe Lin
2022-03-14 23:45 ` Andrew Morton
2022-03-15 13:55 ` Miaohe Lin
2022-03-12 7:46 ` [PATCH v2 3/3] mm/memory-failure.c: make non-LRU movable pages unhandlable Miaohe Lin
2022-03-13 23:43 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2022-03-14 17:34 ` Yang Shi
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=20220313234341.GC3010057@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linmiaohe@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=shy828301@gmail.com \
--cc=tony.luck@intel.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