From: Zi Yan <ziy@nvidia.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Geert Uytterhoeven <geert@linux-m68k.org>,
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: Wed, 04 Dec 2024 11:58:38 -0500 [thread overview]
Message-ID: <B65776A4-D434-4D9F-9C42-1C45DAE5A72A@nvidia.com> (raw)
In-Reply-To: <Z1CDbrrTn6RgNmYn@casper.infradead.org>
On 4 Dec 2024, at 11:29, Matthew Wilcox wrote:
> On Wed, Dec 04, 2024 at 11:16:51AM -0500, Zi Yan wrote:
>>> So maybe the clearing done as part of page allocator isn't enough here.
>>>
>> Basically, mips needs to flush data cache if kmap address is aliased to
>
> People use "aliased" in contronym ways. Do you mean "has a
> non-congruent alias" or "has a congruent alias"?
I mean if kmap address goes into a different cache line than userspace
address, a cache flush is needed to make sure data is visible to
userspace.
>
>> userspace address. This means when mips has THP on, the patch below
>> is not enough to fix the issue.
>>
>> In post_alloc_hook(), it does not make sense to pass userspace address
>> in to determine whether to flush dcache or not.
>>
>> One way to fix it is to add something like arch_userpage_post_alloc()
>> to flush dcache if kmap address is aliased to userspace address.
>> But my questions are that
>> 1) if kmap address will always be the same for two separate kmap_local() calls,
>
> No. It just takes the next address in the stack.
So this fix will not work, since it is possible that first kmap and second
kmap have different pages_do_alias() return values.
Another way would be to make a special case for mips, like below.
But that looks ugly, let me think about it more.
diff --git a/arch/mips/include/asm/page.h b/arch/mips/include/asm/page.h
index bc3e3484c1bf..ef3c6f0b9159 100644
--- a/arch/mips/include/asm/page.h
+++ b/arch/mips/include/asm/page.h
@@ -95,6 +95,19 @@ struct vm_area_struct;
extern void copy_user_highpage(struct page *to, struct page *from,
unsigned long vaddr, struct vm_area_struct *vma);
+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;
+ }
+#define vma_alloc_zeroed_movable_folio vma_alloc_zeroed_movable_folio
+
#define __HAVE_ARCH_COPY_USER_HIGHPAGE
/*
diff --git a/mm/internal.h b/mm/internal.h
index cb8d8e8e3ffa..d513fa683aa3 100644
--- a/mm/internal.h
+++ b/mm/internal.h
@@ -1287,7 +1287,8 @@ void touch_pmd(struct vm_area_struct *vma, unsigned long addr,
static inline bool alloc_zeroed(void)
{
- return static_branch_maybe(CONFIG_INIT_ON_ALLOC_DEFAULT_ON,
+ return !IS_ENABLED(CONFIG_MIPS) &&
+ static_branch_maybe(CONFIG_INIT_ON_ALLOC_DEFAULT_ON,
&init_on_alloc);
}
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2024-12-04 16:58 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 [this message]
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=B65776A4-D434-4D9F-9C42-1C45DAE5A72A@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=geert@linux-m68k.org \
--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 \
/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