Messages in this thread | | | Subject | Re: [PATCH RESEND v2 0/2] riscv: Fix set_memory_XX() and set_direct_map_XX() | From | patchwork-bot+linux-riscv@kernel ... | Date | Wed, 08 Nov 2023 17:20:24 +0000 |
| |
Hello:
This series was applied to riscv/linux.git (for-next) by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 8 Nov 2023 08:59:28 +0100 you wrote: > Those 2 patches fix the set_memory_XX() and set_direct_map_XX() APIs, which > in turn fix STRICT_KERNEL_RWX and memfd_secret(). Those were broken since the > permission changes were not applied to the linear mapping because the linear > mapping is mapped using hugepages and walk_page_range_novma() does not split > such mappings. > > To fix that, patch 1 disables PGD mappings in the linear mapping as it is > hard to propagate changes at this level in *all* the page tables, this has the > downside of disabling PMD mapping for sv32 and PUD (1GB) mapping for sv39 in > the linear mapping (for specific kernels, we could add a Kconfig to enable > ARCH_HAS_SET_DIRECT_MAP and STRICT_KERNEL_RWX if needed, I'm pretty sure we'll > discuss that). > > [...]
Here is the summary with links: - [RESEND,v2,1/2] riscv: Don't use PGD entries for the linear mapping https://git.kernel.org/riscv/c/629db01c64ff - [RESEND,v2,2/2] riscv: Fix set_memory_XX() and set_direct_map_XX() by splitting huge linear mappings https://git.kernel.org/riscv/c/311cd2f6e253
You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
| |