From: Mike Kravetz <mike.kravetz@oracle.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"Michal Hocko" <mhocko@suse.com>
Cc: Muchun Song <songmuchun@bytedance.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"osalvador@suse.de" <osalvador@suse.de>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH] mm: hugetlb: fix a race between memory-failure/soft_offline and gather_surplus_pages
Date: Wed, 21 Apr 2021 11:03:24 -0700 [thread overview]
Message-ID: <57892496-a391-2eb9-eda0-1db9f3b98902@oracle.com> (raw)
In-Reply-To: <20210421083315.GA7552@hori.linux.bs1.fc.nec.co.jp>
On 4/21/21 1:33 AM, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Wed, Apr 21, 2021 at 10:03:34AM +0200, Michal Hocko wrote:
>> [Cc Naoya]
>>
>> On Wed 21-04-21 14:02:59, Muchun Song wrote:
>>> The possible bad scenario:
>>>
>>> CPU0: CPU1:
>>>
>>> gather_surplus_pages()
>>> page = alloc_surplus_huge_page()
>>> memory_failure_hugetlb()
>>> get_hwpoison_page(page)
>>> __get_hwpoison_page(page)
>>> get_page_unless_zero(page)
>>> zero = put_page_testzero(page)
>>> VM_BUG_ON_PAGE(!zero, page)
>>> enqueue_huge_page(h, page)
>>> put_page(page)
>>>
>>> The refcount can possibly be increased by memory-failure or soft_offline
>>> handlers, we can trigger VM_BUG_ON_PAGE and wrongly add the page to the
>>> hugetlb pool list.
>>
>> The hwpoison side of this looks really suspicious to me. It shouldn't
>> really touch the reference count of hugetlb pages without being very
>> careful (and having hugetlb_lock held).
>
> I have the same feeling, there is a window where a hugepage is refcounted
> during converting from buddy free pages into free hugepage, so refcount
> alone is not enough to prevent the race. hugetlb_lock is retaken after
> alloc_surplus_huge_page returns, so simply holding hugetlb_lock in
> get_hwpoison_page() seems not work. Is there any status bit to show that a
> hugepage is just being initialized (not in free hugepage pool or in use)?
>
It seems we can also race with the code that makes a compound page a
hugetlb page. The memory failure code could be called after allocating
pages from buddy and before setting compound page DTOR. So, the memory
handling code will process it as a compound page.
Just thinking that this may not be limited to the hugetlb specific memory
failure handling?
--
Mike Kravetz
next prev parent reply other threads:[~2021-04-21 18:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 6:02 Muchun Song
2021-04-21 8:03 ` Michal Hocko
2021-04-21 8:15 ` [External] " Muchun Song
2021-04-21 8:21 ` Oscar Salvador
2021-04-21 8:41 ` Muchun Song
2021-04-21 8:49 ` Oscar Salvador
2021-04-21 8:58 ` Muchun Song
2021-04-21 8:43 ` Michal Hocko
2021-04-21 8:25 ` Michal Hocko
2021-04-21 8:33 ` HORIGUCHI NAOYA(堀口 直也)
2021-04-21 9:02 ` [External] " Muchun Song
2021-04-21 18:03 ` Mike Kravetz [this message]
2021-04-22 8:27 ` HORIGUCHI NAOYA(堀口 直也)
2021-04-23 8:01 ` HORIGUCHI NAOYA(堀口 直也)
2021-04-28 7:46 ` [PATCH] mm,hwpoison: fix race with compound page allocation Naoya Horiguchi
2021-04-28 8:23 ` Oscar Salvador
2021-04-28 9:18 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-06 1:31 ` [PATCH v2] " Naoya Horiguchi
2021-05-06 8:51 ` Oscar Salvador
2021-05-07 4:17 ` HORIGUCHI NAOYA(堀口 直也)
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=57892496-a391-2eb9-eda0-1db9f3b98902@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=songmuchun@bytedance.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