Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH -fixes] riscv: Do not allow vmap pud mappings for 3-level page
 table
From:   patchwork-bot+linux-riscv@kernel.org
Message-Id: <169169702217.10459.13892718151102132616.git-patchwork-notify@kernel.org>
Date:   Thu, 10 Aug 2023 19:50:22 +0000
References: <20230808130709.1502614-1-alexghiti@rivosinc.com>
In-Reply-To: <20230808130709.1502614-1-alexghiti@rivosinc.com>
To:     Alexandre Ghiti <alexghiti@rivosinc.com>
Cc:     linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
        palmer@dabbelt.com, aou@eecs.berkeley.edu, bjorn@rivosinc.com,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.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