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 v4] riscv: fix race when vmap stack overflow
From:   patchwork-bot+linux-riscv@kernel.org
Message-Id: <166992541746.24789.931668146499412553.git-patchwork-notify@kernel.org>
Date:   Thu, 01 Dec 2022 20:10:17 +0000
References: <20221130022442.18358-1-palmer@rivosinc.com>
In-Reply-To: <20221130022442.18358-1-palmer@rivosinc.com>
To:     Palmer Dabbelt <palmer@rivosinc.com>
Cc:     linux-riscv@lists.infradead.org, jszhang@kernel.org,
        guoren@kernel.org, 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, 29 Nov 2022 18:24:43 -0800 you wrote:
> From: Jisheng Zhang <jszhang@kernel.org>
> 
> Currently, when detecting vmap stack overflow, riscv firstly switches
> to the so called shadow stack, then use this shadow stack to call the
> get_overflow_stack() to get the overflow stack. However, there's
> a race here if two or more harts use the same shadow stack at the same
> time.
> 
> [...]

Here is the summary with links:
  - [v4] riscv: fix race when vmap stack overflow
    https://git.kernel.org/riscv/c/7e1864332fbc

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