Peter Zijlstra 169950cfb4 x86/mm: Fix pti_clone_pgtable() alignment assumption ... [ Upstream commit 41e71dbb0e0a0fe214545fe64af031303a08524c ] Guenter reported dodgy crashes on an i386-nosmp build using GCC-11 that had the form of endless traps until entry stack exhaust and then #DF from the stack guard. It turned out that pti_clone_pgtable() had alignment assumptions on the start address, notably it hard assumes start is PMD aligned. This is true on x86_64, but very much not true on i386. These assumptions can cause the end condition to malfunction, leading to a 'short' clone. Guess what happens when the user mapping has a short copy of the entry text? Use the correct increment form for addr to avoid alignment assumptions. Fixes: 16a3fe634f6a ("x86/mm/pti: Clone kernel-image on PTE level for 32 bit") Reported-by: Guenter Roeck <linux@roeck-us.net> Tested-by: Guenter Roeck <linux@roeck-us.net> Suggested-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lkml.kernel.org/r/20240731163105.GG33588@noisy.programming.kicks-ass.net Signed-off-by: Sasha Levin <sashal@kernel.org>		2024-11-23 23:20:21 +01:00
..
pat
amdtopology.c
cpu_entry_area.c
debug_pagetables.c
dump_pagetables.c
extable.c
fault.c
highmem_32.c
hugetlbpage.c
ident_map.c
init.c
init_32.c
init_64.c
iomap_32.c
ioremap.c
kasan_init_64.c
kaslr.c
kmmio.c
maccess.c
Makefile
mem_encrypt.c
mem_encrypt_boot.S
mem_encrypt_identity.c
mm_internal.h
mmap.c
mmio-mod.c
numa.c
numa_32.c
numa_64.c
numa_emulation.c
numa_internal.h
pf_in.c
pf_in.h
pgtable.c
pgtable_32.c
physaddr.c
physaddr.h
pkeys.c
pti.c	x86/mm: Fix pti_clone_pgtable() alignment assumption	2024-11-23 23:20:21 +01:00
setup_nx.c
srat.c
testmmiotrace.c
tlb.c