From: Zi Yan <ziy@nvidia.com>
To: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Miaohe Lin <linmiaohe@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
John Hubbard <jhubbard@nvidia.com>,
"Huang, Ying" <ying.huang@intel.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Alexander Potapenko <glider@google.com>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, Zi Yan <ziy@nvidia.com>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm: avoid zeroing user movable page twice with init_on_alloc=1
Date: Fri, 11 Oct 2024 14:23:56 -0400 [thread overview]
Message-ID: <9ED14870-39CF-40CA-875F-3A7FDE4D7DF3@nvidia.com> (raw)
In-Reply-To: <20241011150304.709590-1-ziy@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 3357 bytes --]
+Vlastimil
On 11 Oct 2024, at 11:03, Zi Yan wrote:
> Commit 6471384af2a6 ("mm: security: introduce init_on_alloc=1 and
> init_on_free=1 boot options") forces allocated page to be zeroed in
> post_alloc_hook() when init_on_alloc=1.
>
> For order-0 folios, if arch does not define
> vma_alloc_zeroed_movable_folio(), the default implementation again zeros
> the page return from the buddy allocator. So the page is zeroed twice.
> Fix it by passing __GFP_ZERO instead to avoid double page zeroing.
> At the moment, s390,arm64,x86,alpha,m68k are not impacted since they
> define their own vma_alloc_zeroed_movable_folio().
>
> For >0 order folios (mTHP and PMD THP), folio_zero_user() is called to
> zero the folio again. Fix it by calling folio_zero_user() only if
> init_on_alloc is set. All arch are impacted.
>
> Added alloc_zeroed() helper to encapsulate the init_on_alloc check.
>
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> ---
> include/linux/highmem.h | 8 +-------
> mm/huge_memory.c | 3 ++-
> mm/internal.h | 6 ++++++
> mm/memory.c | 3 ++-
> 4 files changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/highmem.h b/include/linux/highmem.h
> index bec9bd715acf..6e452bd8e7e3 100644
> --- a/include/linux/highmem.h
> +++ b/include/linux/highmem.h
> @@ -224,13 +224,7 @@ static inline
> struct folio *vma_alloc_zeroed_movable_folio(struct vm_area_struct *vma,
> unsigned long vaddr)
> {
> - struct folio *folio;
> -
> - folio = vma_alloc_folio(GFP_HIGHUSER_MOVABLE, 0, vma, vaddr);
> - if (folio)
> - clear_user_highpage(&folio->page, vaddr);
> -
> - return folio;
> + return vma_alloc_folio(GFP_HIGHUSER_MOVABLE | __GFP_ZERO, 0, vma, vaddr);
> }
> #endif
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index 82f464865570..5dcbea96edb7 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -1176,7 +1176,8 @@ static struct folio *vma_alloc_anon_folio_pmd(struct vm_area_struct *vma,
> }
> folio_throttle_swaprate(folio, gfp);
>
> - folio_zero_user(folio, addr);
> + if (!alloc_zeroed())
> + folio_zero_user(folio, addr);
> /*
> * The memory barrier inside __folio_mark_uptodate makes sure that
> * folio_zero_user writes become visible before the set_pmd_at()
> diff --git a/mm/internal.h b/mm/internal.h
> index 906da6280c2d..508f7802dd2b 100644
> --- a/mm/internal.h
> +++ b/mm/internal.h
> @@ -1233,6 +1233,12 @@ void touch_pud(struct vm_area_struct *vma, unsigned long addr,
> void touch_pmd(struct vm_area_struct *vma, unsigned long addr,
> pmd_t *pmd, bool write);
>
> +static inline bool alloc_zeroed(void)
> +{
> + return static_branch_maybe(CONFIG_INIT_ON_ALLOC_DEFAULT_ON,
> + &init_on_alloc);
> +}
> +
> enum {
> /* mark page accessed */
> FOLL_TOUCH = 1 << 16,
> diff --git a/mm/memory.c b/mm/memory.c
> index c67359ddb61a..88252f0e06d0 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -4719,7 +4719,8 @@ static struct folio *alloc_anon_folio(struct vm_fault *vmf)
> goto next;
> }
> folio_throttle_swaprate(folio, gfp);
> - folio_zero_user(folio, vmf->address);
> + if (!alloc_zeroed())
> + folio_zero_user(folio, vmf->address);
> return folio;
> }
> next:
> --
> 2.45.2
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2024-10-11 18:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 15:03 Zi Yan
2024-10-11 18:23 ` Zi Yan [this message]
2024-10-16 12:53 ` Vlastimil Babka
2024-10-16 13:30 ` Zi Yan
2024-10-21 12:23 ` David Hildenbrand
2024-10-21 14:21 ` Zi Yan
2024-10-22 14:33 ` Zi Yan
2024-12-04 10:41 ` Geert Uytterhoeven
2024-12-04 12:50 ` Zi Yan
2024-12-04 12:56 ` Geert Uytterhoeven
2024-12-04 15:24 ` Zi Yan
2024-12-04 15:41 ` Vlastimil Babka
2024-12-04 16:16 ` Zi Yan
2024-12-04 16:29 ` Matthew Wilcox
2024-12-04 16:58 ` Zi Yan
2024-12-05 8:19 ` Geert Uytterhoeven
2024-12-05 17:32 ` Zi Yan
2024-12-06 8:37 ` Geert Uytterhoeven
2024-12-04 17:33 ` Zi Yan
2024-12-04 17:46 ` Vlastimil Babka
2024-12-04 18:13 ` Zi Yan
2024-12-04 18:16 ` Zi Yan
2024-12-04 21:21 ` Zi Yan
2024-12-04 21:24 ` John Hubbard
2024-12-04 18:30 ` Zi Yan
2024-12-05 8:04 ` Geert Uytterhoeven
2024-12-05 8:10 ` David Hildenbrand
2024-12-05 16:05 ` Zi Yan
2024-12-05 17:24 ` Vlastimil Babka
2024-12-05 17:38 ` Zi Yan
2024-12-06 8:03 ` Geert Uytterhoeven
2024-12-05 8:15 ` Geert Uytterhoeven
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=9ED14870-39CF-40CA-875F-3A7FDE4D7DF3@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=glider@google.com \
--cc=jhubbard@nvidia.com \
--cc=keescook@chromium.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox