From: patchwork-bot+linux-riscv@kernel.org
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, jszhang@kernel.org,
guoren@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] riscv: fix race when vmap stack overflow
Date: Thu, 01 Dec 2022 20:10:17 +0000 [thread overview]
Message-ID: <166992541746.24789.931668146499412553.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221130022442.18358-1-palmer@rivosinc.com>
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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-12-01 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 2:24 [PATCH v4] riscv: fix race when vmap stack overflow Palmer Dabbelt
2022-11-30 7:15 ` Guo Ren
2022-11-30 16:54 ` Palmer Dabbelt
2022-12-01 1:17 ` Guo Ren
2022-12-01 1:55 ` Jessica Clarke
2022-12-01 2:43 ` Andrea Parri
2022-12-01 20:00 ` Palmer Dabbelt
2022-12-01 20:10 ` patchwork-bot+linux-riscv [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=166992541746.24789.931668146499412553.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox