On Mon, 29 Jun 2020 11:15:19 +0000 (UTC), Christophe Leroy wrote: > On book3s32 (hash), exec protection is set per 256Mb segments with NX bit. > Instead of clearing NX bit on vmalloc space when CONFIG_MODULES is selected, > allocate modules in a dedicated segment (0xb0000000-0xbfffffff by default). > This allows to keep exec protection on vmalloc space while allowing exec > on modules. > > v2: > - Removed the two patches that fix ptdump. Will submitted independently > - Only changing the user/kernel boundary for PPC32 now. > - Reordered the patches inside the series. > > [...]
Applied to powerpc/next. [1/6] powerpc/lib: Prepare code-patching for modules allocated outside vmalloc space https://git.kernel.org/powerpc/c/ccc8fcf72a6953fbfd6998999d622295f522b952 [2/6] powerpc: Use MODULES_VADDR if defined https://git.kernel.org/powerpc/c/7fbc22ce29931630da200cfc90fe5a454f54a794 [3/6] powerpc/32s: Only leave NX unset on segments used for modules https://git.kernel.org/powerpc/c/c496433197154144c310a17939736bc5c155914d [4/6] powerpc/32: Set user/kernel boundary at TASK_SIZE instead of PAGE_OFFSET https://git.kernel.org/powerpc/c/b6be1bb7f7216b9e9f33f57abe6e3290c0e66bd4 [5/6] powerpc/32s: Kernel space starts at TASK_SIZE https://git.kernel.org/powerpc/c/f1a1f7a15eb0e13b84791ff2738b84e414501718 [6/6] powerpc/32s: Use dedicated segment for modules with STRICT_KERNEL_RWX https://git.kernel.org/powerpc/c/6ca055322da8fe25ff9ac50db6f3b7b59b6f961c cheers