> On Wednesday, February 21, 2024 at 1:32 AM, Christophe Leroy wrote:
>
> On powerpc (book3s/32) we have more or less the same although it is not
> directly linked to PMDs: the virtual 4G address space is split in
> segments of 256M. On each segment there's a bit called NX to forbit
> execution. V
> From: Conor Dooley
> FYI:
>
> > mm/vmalloc: allow arch-specific vmalloc_node overrides
> > mm: pgalloc: support address-conditional pmd allocation
>
> With these two arch/riscv/configs/* are broken with calls to undeclared
> functions.
Will fix, thanks! I will also figure out how to make
Hey Maxwell,
FYI:
> mm/vmalloc: allow arch-specific vmalloc_node overrides
> mm: pgalloc: support address-conditional pmd allocation
With these two arch/riscv/configs/* are broken with calls to undeclared
functions.
> arm64: separate code and data virtual memory allocation
> arm64: dyna
Le 20/02/2024 à 21:32, Maxwell Bland a écrit :
> [Vous ne recevez pas souvent de courriers de mbl...@motorola.com. Découvrez
> pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ]
>
> Reworks ARM's virtual memory allocation infrastructure to support
> dynamic enforcemen
Reworks ARM's virtual memory allocation infrastructure to support
dynamic enforcement of page middle directory PXNTable restrictions
rather than only during the initial memory mapping. Runtime enforcement
of this bit prevents write-then-execute attacks, where malicious code is
staged in vmalloc'd d
