From: David Hildenbrand <david@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: Restrict and formalize compound_page_dtors[]
Date: Mon, 18 May 2020 12:05:21 +0200 [thread overview]
Message-ID: <3261e416-2454-d6c5-a962-724df39cdbab@redhat.com> (raw)
In-Reply-To: <1589795958-19317-1-git-send-email-anshuman.khandual@arm.com>
On 18.05.20 11:59, Anshuman Khandual wrote:
> Restrict elements in compound_page_dtors[] array per NR_COMPOUND_DTORS and
> explicitly position them according to enum compound_dtor_id. This improves
> protection against possible misalignment between compound_page_dtors[] and
> enum compound_dtor_id later on.
>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> include/linux/mm.h | 2 +-
> mm/page_alloc.c | 10 +++++-----
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 688558c57751..d1bd7736a5e5 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -856,7 +856,7 @@ enum compound_dtor_id {
> #endif
> NR_COMPOUND_DTORS,
> };
> -extern compound_page_dtor * const compound_page_dtors[];
> +extern compound_page_dtor * const compound_page_dtors[NR_COMPOUND_DTORS];
>
> static inline void set_compound_page_dtor(struct page *page,
> enum compound_dtor_id compound_dtor)
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index cef05d3a23f5..2e4c23b34940 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -302,14 +302,14 @@ const char * const migratetype_names[MIGRATE_TYPES] = {
> #endif
> };
>
> -compound_page_dtor * const compound_page_dtors[] = {
> - NULL,
> - free_compound_page,
> +compound_page_dtor * const compound_page_dtors[NR_COMPOUND_DTORS] = {
> + [NULL_COMPOUND_DTOR] = NULL,
> + [COMPOUND_PAGE_DTOR] = free_compound_page,
> #ifdef CONFIG_HUGETLB_PAGE
> - free_huge_page,
> + [HUGETLB_PAGE_DTOR] = free_huge_page,
> #endif
> #ifdef CONFIG_TRANSPARENT_HUGEPAGE
> - free_transhuge_page,
> + [TRANSHUGE_PAGE_DTOR] = free_transhuge_page,
> #endif
> };
>
>
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2020-05-18 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 9:59 [PATCH] mm/page_alloc: Restrict and formalize compound_page_dtors[] Anshuman Khandual
2020-05-18 10:05 ` David Hildenbrand [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=3261e416-2454-d6c5-a962-724df39cdbab@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.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).