From: Mike Kravetz <mike.kravetz@oracle.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Naoya Horiguchi <nao.horiguchi@gmail.com>,
linux-mm@kvack.org, Oscar Salvador <osalvador@suse.de>,
Muchun Song <songmuchun@bytedance.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] hugetlb: pass head page to remove_hugetlb_page()
Date: Thu, 27 May 2021 14:12:21 -0700 [thread overview]
Message-ID: <cfd46177-16b7-7eac-0845-41109552044a@oracle.com> (raw)
In-Reply-To: <YK/44mOnwZgUOdYA@dhcp22.suse.cz>
On 5/27/21 12:54 PM, Michal Hocko wrote:
> On Thu 27-05-21 09:28:51, Mike Kravetz wrote:
>> On 5/26/21 4:52 PM, Naoya Horiguchi wrote:
>>> From: Naoya Horiguchi <naoya.horiguchi@nec.com>
>>>
>>> remove_hugetlb_page() dereferences page->lru, so it's assumed that the
>>> page points to a head page, but one of the caller,
>>> dissolve_free_huge_page(), provides remove_hugetlb_page() with 'page'
>>> which could be a tail page. So pass 'head' to it, instead.
>>>
>>
>> I believe we have the same problem later in the routine when calling
>> add_hugetlb_page()?
>
> Can we ever get a tail page there?
>
Yes. Actually alloc_huge_page_vmemmap() and add_hugetlb_page() calls
later in the same block of code expect head page but we pass 'page' which
could be a tail page.
>> If so, should we combine the changes? Or, do we need two patches as
>> the bugs were introduced with different commits?
>
> If there is an issue then I would go with a separate patch.
>
The calls to alloc_huge_page_vmemmap() and add_hugetlb_page() are only
in Andrew's tree (and next). So, they can be fixed there.
I'll send a patch shortly.
--
Mike Kravetz
prev parent reply other threads:[~2021-05-27 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 23:52 Naoya Horiguchi
2021-05-27 0:31 ` Matthew Wilcox
2021-05-27 0:55 ` Mike Kravetz
2021-05-27 2:43 ` [External] " Muchun Song
2021-05-27 6:58 ` Michal Hocko
2021-05-27 7:47 ` Oscar Salvador
2021-05-27 8:22 ` Michal Hocko
2021-05-27 16:28 ` Mike Kravetz
2021-05-27 19:54 ` Michal Hocko
2021-05-27 21:12 ` Mike Kravetz [this message]
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=cfd46177-16b7-7eac-0845-41109552044a@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.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