linux-kernel - Re: [PATCH -fixes] riscv: Do not allow vmap pud mappings for 3-level page table

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 10 Aug 2023 19:50:22 +0000
From:   patchwork-bot+linux-riscv@...nel.org
To:     Alexandre Ghiti <alexghiti@...osinc.com>
Cc:     linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com,
        palmer@...belt.com, aou@...s.berkeley.edu, bjorn@...osinc.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH -fixes] riscv: Do not allow vmap pud mappings for 3-level page
 table

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@...osinc.com>:

On Tue,  8 Aug 2023 15:07:09 +0200 you wrote:
> The vmalloc_fault() path was removed and to avoid syncing the vmalloc PGD
> mappings, they are now preallocated. But if the kernel can use a PUD
> mapping (which in sv39 is actually a PGD mapping) for large vmalloc
> allocation, it will free the current unused preallocated PGD mapping and
> install a new leaf one. Since there is no sync anymore, some page tables
> lack this new mapping and that triggers a panic.
> 
> [...]

Here is the summary with links:
  - [-fixes] riscv: Do not allow vmap pud mappings for 3-level page table
    https://git.kernel.org/riscv/c/d566bea4a638

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html