From: Oscar Salvador <osalvador@suse.de>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: Mike Kravetz <mike.kravetz@oracle.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Muchun Song <songmuchun@bytedance.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Tony Luck <tony.luck@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/2] mm,hwpoison: fix race with hugetlb page allocation
Date: Tue, 25 May 2021 09:36:05 +0200 [thread overview]
Message-ID: <20210525073559.GA844@linux> (raw)
In-Reply-To: <20210520071717.GA2641190@hori.linux.bs1.fc.nec.co.jp>
On Thu, May 20, 2021 at 07:17:17AM +0000, HORIGUCHI NAOYA(堀口 直也) wrote:
> So I think of inserting the check to comply with the assumption of
> get_hwpoison_huge_page() like below:
>
> ret = get_hwpoison_huge_page(head, &hugetlb);
> if (hugetlb)
> return ret;
>
> if (!PageLRU(head) && !__PageMovable(head))
> return 0;
>
> if (PageTransHuge(head)) {
> ...
> }
>
> if (get_page_unless_zero(head)) {
> ...
> }
>
> return 0;
Hi Naoya,
would you mind posting a complete draft of what it would look like?
I am having a hard time picturing it.
Thanks
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2021-05-25 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 23:12 [PATCH v5 0/2] hwpoison: fix race with hugetlb page allocation Naoya Horiguchi
2021-05-18 23:12 ` [PATCH v5 1/2] mm,hwpoison: " Naoya Horiguchi
2021-05-19 22:32 ` Mike Kravetz
2021-05-20 7:17 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-25 7:36 ` Oscar Salvador [this message]
2021-05-25 8:07 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-25 9:09 ` Oscar Salvador
2021-05-25 13:08 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-18 23:12 ` [PATCH v5 2/2] mm,hwpoison: make get_hwpoison_page call get_any_page() Naoya Horiguchi
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=20210525073559.GA844@linux \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=nao.horiguchi@gmail.com \
--cc=naoya.horiguchi@nec.com \
--cc=songmuchun@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.