linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Zi Yan <ziy@nvidia.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	linux-mm@kvack.org,  Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.com>,
	 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,  linux-mips@vger.kernel.org
Subject: Re: [PATCH] mm: avoid zeroing user movable page twice with init_on_alloc=1
Date: Fri, 6 Dec 2024 09:37:12 +0100	[thread overview]
Message-ID: <CAMuHMdXbugTBrK5yqRB6ysHcEq8POCu3O37BUPU4i-8rLsQY2g@mail.gmail.com> (raw)
In-Reply-To: <EF8F5058-83CA-45FE-8721-08224B489361@nvidia.com>

Hi Zi,

On Thu, Dec 5, 2024 at 6:33 PM Zi Yan <ziy@nvidia.com> wrote:
> Can you try the patch below (it compiles locally for mips and x86) to see
> if your issue is fixed? Can you please make THP always on in your config,
> since THP is also affected by the same issue? The patch you tested only
> fixed non THP config.

Thanks, this works both without THP, and with
CONFIG_TRANSPARENT_HUGEPAGE=y
CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y

Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>

> Thanks. I appreciate your help. :)

Thanks, I appreciate your quick responses and solutions!

> --- a/include/linux/highmem.h
> +++ b/include/linux/highmem.h
> @@ -224,7 +224,13 @@ static inline
>  struct folio *vma_alloc_zeroed_movable_folio(struct vm_area_struct *vma,
>                                    unsigned long vaddr)
>  {
> -       return vma_alloc_folio(GFP_HIGHUSER_MOVABLE | __GFP_ZERO, 0, vma, vaddr);
> +       struct folio *folio;
> +
> +       folio = vma_alloc_folio(GFP_HIGHUSER_MOVABLE, 0, vma, vaddr);
> +       if (folio && alloc_need_zeroing())
> +               clear_user_highpage(&folio->page, vaddr);
> +
> +       return folio;
>  }
>  #endif
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index c39c4945946c..6ac0308c4380 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -4175,6 +4175,23 @@ static inline int do_mseal(unsigned long start, size_t len_in, unsigned long fla
>  }
>  #endif
>
> +/*
> + * alloc_need_zeroing checks if a user folio from page allocator needs to be
> + * zeroed or not.
> + */
> +static inline bool alloc_need_zeroing(void)
> +{
> +       /*
> +        * for user folios, arch with cache aliasing requires cache flush and
> +        * arc sets folio->flags, so always return false to make caller use
> +        * clear_user_page()/clear_user_highpage()
> +        */
> +       return (IS_ENABLED(CONFIG_ARCH_HAS_CPU_CACHE_ALIASING) ||
> +               IS_ENABLED(CONFIG_ARC)) ||
> +              !static_branch_maybe(CONFIG_INIT_ON_ALLOC_DEFAULT_ON,
> +                                  &init_on_alloc);
> +}
> +
>  int arch_get_shadow_stack_status(struct task_struct *t, unsigned long __user *status);
>  int arch_set_shadow_stack_status(struct task_struct *t, unsigned long status);
>  int arch_lock_shadow_stack_status(struct task_struct *t, unsigned long status);
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index ee335d96fc39..107130a5413a 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -1176,11 +1176,12 @@ static struct folio *vma_alloc_anon_folio_pmd(struct vm_area_struct *vma,
>         folio_throttle_swaprate(folio, gfp);
>
>         /*
> -       * When a folio is not zeroed during allocation (__GFP_ZERO not used),
> -       * folio_zero_user() is used to make sure that the page corresponding
> -       * to the faulting address will be hot in the cache after zeroing.
> +       * When a folio is not zeroed during allocation (__GFP_ZERO not used)
> +       * or user folios require special handling, folio_zero_user() is used to
> +       * make sure that the page corresponding to the faulting address will be
> +       * hot in the cache after zeroing.
>         */
> -       if (!alloc_zeroed())
> +       if (alloc_need_zeroing())
>                 folio_zero_user(folio, addr);
>         /*
>          * The memory barrier inside __folio_mark_uptodate makes sure that
> diff --git a/mm/internal.h b/mm/internal.h
> index cb8d8e8e3ffa..3bd08bafad04 100644
> --- a/mm/internal.h
> +++ b/mm/internal.h
> @@ -1285,12 +1285,6 @@ 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);
> -}
> -
>  /*
>   * Parses a string with mem suffixes into its order. Useful to parse kernel
>   * parameters.
> diff --git a/mm/memory.c b/mm/memory.c
> index 75c2dfd04f72..cf1611791856 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -4733,12 +4733,12 @@ static struct folio *alloc_anon_folio(struct vm_fault *vmf)
>                         folio_throttle_swaprate(folio, gfp);
>                         /*
>                          * When a folio is not zeroed during allocation
> -                        * (__GFP_ZERO not used), folio_zero_user() is used
> -                        * to make sure that the page corresponding to the
> -                        * faulting address will be hot in the cache after
> -                        * zeroing.
> +                        * (__GFP_ZERO not used) or user folios require special
> +                        * handling, folio_zero_user() is used to make sure
> +                        * that the page corresponding to the faulting address
> +                        * will be hot in the cache after zeroing.
>                          */
> -                       if (!alloc_zeroed())
> +                       if (alloc_need_zeroing())
>                                 folio_zero_user(folio, vmf->address);
>                         return folio;
>                 }

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds


  reply	other threads:[~2024-12-06  8:37 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
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 [this message]
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=CAMuHMdXbugTBrK5yqRB6ysHcEq8POCu3O37BUPU4i-8rLsQY2g@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --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-mips@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 \
    --cc=ziy@nvidia.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