From: Dave Hansen <dave.hansen@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
bp@alien8.de, joro@8bytes.org, luto@kernel.org,
kirill.shutemov@linux.intel.com, rick.p.edgecombe@intel.com,
jgross@suse.com
Subject: Re: [RFC][PATCH 0/8] x86/mm: Simplify PAE page table handling
Date: Thu, 23 Jan 2025 15:06:26 -0800 [thread overview]
Message-ID: <6c1785c8-e74e-4912-95bb-88b6e94f544f@intel.com> (raw)
In-Reply-To: <20250123214911.GB969@noisy.programming.kicks-ass.net>
On 1/23/25 13:49, Peter Zijlstra wrote:
> On Thu, Jan 23, 2025 at 09:24:28AM -0800, Dave Hansen wrote:
>> tl;dr: 32-bit PAE page table handing is a bit different when PTI
>> is on and off. Making the handling uniform removes a good amount
>> of code at the cost of not sharing kernel PMDs. The downside of
>> this simplification is bloating non-PTI PAE kernels by ~2 pages
>> per process.
>>
>> Anyone who cares about security on 32-bit is running with PTI and
>> PAE because PAE has the No-eXecute page table bit. They are already
>> paying the 2-page penalty. Anyone who cares more about memory
>> footprint than security is probably already running a !PAE kernel
>> and will not be affected by this.
>
> The reality is that many of the mitigations we have are 64bit only.
> 32bit is known insecure. There is absolutely no point in using PTI on
> 32bit at all.
>
> Can't we just rip it out?
32-bit+PTI or 32-bit in general? ;)
I'm curious what Joerg and the other folks that worked on 32-bit PTI
think about it in retrospect. The 32 vs. 64-bit security gap was
probably modest in 2018 and it can only have grown since then.
I definitely haven't seen a lot of 32-bit PTI bug reports.
next prev parent reply other threads:[~2025-01-23 23:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 17:24 Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 1/8] x86/mm: Always allocate a whole page for PAE PGDs Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 2/8] x86/mm: Always "broadcast" PMD setting operations Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 3/8] x86/mm: Always tell core mm to sync kernel mappings Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 4/8] x86/mm: Simplify PAE PGD sharing macros Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 5/8] x86/mm: Fix up comments around PMD preallocation Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 6/8] x86/mm: Preallocate all PAE page tables Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 7/8] x86/mm: Remove duplicated PMD preallocation macro Dave Hansen
2025-01-23 17:24 ` [RFC][PATCH 8/8] x86/mm: Remove now unused SHARED_KERNEL_PMD Dave Hansen
2025-01-23 21:49 ` [RFC][PATCH 0/8] x86/mm: Simplify PAE page table handling Peter Zijlstra
2025-01-23 23:06 ` Dave Hansen [this message]
2025-01-24 7:58 ` Joerg Roedel
2025-01-24 19:12 ` Dave Hansen
2025-01-28 8:13 ` Joerg Roedel
2025-01-24 8:52 ` Peter Zijlstra
2025-02-24 18:55 ` Ingo Molnar
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=6c1785c8-e74e-4912-95bb-88b6e94f544f@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®