From: Vlastimil Babka <vbabka@suse.cz>
To: Zi Yan <ziy@nvidia.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
David Hildenbrand <david@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.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, linux-mips@vger.kernel.org
Subject: Re: [PATCH] mm: avoid zeroing user movable page twice with init_on_alloc=1
Date: Thu, 5 Dec 2024 18:24:50 +0100 [thread overview]
Message-ID: <434596ce-5514-42f3-84f5-f8a70954f058@suse.cz> (raw)
In-Reply-To: <F3805AF4-1660-4CEA-868E-2D1F4A70BCB3@nvidia.com>
On 12/5/24 17:05, Zi Yan wrote:
> On 5 Dec 2024, at 3:10, David Hildenbrand wrote:
>>>
>>> Kernel log confirms it's enabled:
>>> -mem auto-init: stack:off, heap alloc:off, heap free:off
>>> +mem auto-init: stack:off, heap alloc:on, heap free:off
>>
>> If I'm not wrong that's expected ... because we'll be double-zeroing that memory, clearing the cache :)
>>
>> I guess the question is, how *effective* is CONFIG_INIT_ON_ALLOC_DEFAULT_ON on systems to prevent exposing un-zeroed data to userspace, when it doesn't end up doing the flush we really need.
>
> Hi Geert,
>
> Is it possible to run a 32bit kernel with HIGHMEM and
> CONFIG_INIT_ON_ALLOC_DEFAULT_ON on the machine (of course with my patch
> reverted)? Just to check my reasoning below.
>
> Thanks.
>
>
> Yes, it should work, since I forgot the actual issue is HIGHMEM+cache flush, not just cache flush is needed after clearing user page.
>
> For arch which needs to flush cache after clearing user page, with HIGHMEM,
> init_on_alloc first clears the page using kmap_addr0 without flushing
> the cache, then clear_user_page() clears the page using kmap_addr1
> with cache flush. After returning to userspace, the cache lines of
> kmap_addr0 will be evicted and written back to RAM eventually, corrupting
> user data with 0s, because no one flushes them before returning to userspace.
>
> For a proper fix, I will add ARCH_HAS_OPS_AFTER_CLEAR_USER_PAGE and
> make mips, sh, sparc, arm, xtensa, nios2, m68k, parisc, csky, arc, and powerpc
> select it, then make alloc_zeroed() returns false if
> ARCH_HAS_OPS_AFTER_CLEAR_USER_PAGE is enabled.
>
> If my reasoning above is verified to be true, I will send a separate patch
> to disable CONFIG_INIT_ON_ALLOC_DEFAULT_ON if HIGHMEM &&
> ARCH_HAS_OPS_AFTER_CLEAR_USER_PAGE.
If your reasoning is true, wouldn't any other user of kmap_local_page() of a
highpage on such system also leave the cache unflushed in case the page is
ever reused as a userspace page?
> Best Regards,
> Yan, Zi
next prev parent reply other threads:[~2024-12-05 17: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
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 [this message]
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=434596ce-5514-42f3-84f5-f8a70954f058@suse.cz \
--to=vbabka@suse.cz \
--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=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