From: Andrew Morton <akpm@linux-foundation.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Joao Martins <joao.m.martins@oracle.com>
Subject: Re: [PATCH] mm/page_alloc: make calling prep_compound_head more reliable
Date: Tue, 7 Jun 2022 11:32:57 -0700 [thread overview]
Message-ID: <20220607113257.84b1bdd993f19be26b8c4944@linux-foundation.org> (raw)
In-Reply-To: <20220607144157.36411-1-linmiaohe@huawei.com>
Let's cc Joao.
On Tue, 7 Jun 2022 22:41:57 +0800 Miaohe Lin <linmiaohe@huawei.com> wrote:
> compound_pincount_ptr is stored at first tail page instead of second tail
> page now.
"now"? Some identifiable commit did this?
> And if it or some other field changes again in the future, data
> overwritten might happen. Calling prep_compound_head() outside the loop
> to prevent such possible issue. No functional change intended.
>
> ...
>
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -6772,17 +6772,8 @@ static void __ref memmap_init_compound(struct page *head,
> __init_zone_device_page(page, pfn, zone_idx, nid, pgmap);
> prep_compound_tail(head, pfn - head_pfn);
> set_page_count(page, 0);
> -
> - /*
> - * The first tail page stores compound_mapcount_ptr() and
> - * compound_order() and the second tail page stores
> - * compound_pincount_ptr(). Call prep_compound_head() after
> - * the first and second tail pages have been initialized to
> - * not have the data overwritten.
> - */
> - if (pfn == head_pfn + 2)
> - prep_compound_head(head, order);
> }
> + prep_compound_head(head, order);
> }
>
> void __ref memmap_init_zone_device(struct zone *zone,
next prev parent reply other threads:[~2022-06-07 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 14:41 [PATCH] mm/page_alloc: make calling prep_compound_head more reliable Miaohe Lin
2022-06-07 18:32 ` Andrew Morton [this message]
2022-06-07 19:17 ` Joao Martins
2022-06-08 12:17 ` Miaohe Lin
2022-06-14 13:13 ` Matthew Wilcox
2022-06-15 7:44 ` Miaohe Lin
2022-06-15 12:42 ` Matthew Wilcox
2022-06-16 3:21 ` Miaohe Lin
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=20220607113257.84b1bdd993f19be26b8c4944@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=joao.m.martins@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).