From: patchwork-bot+linux-riscv@kernel.org
To: Sami Tolvanen <samitolvanen@google.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, keescook@chromium.org,
cleger@rivosinc.com, guoren@kernel.org, debug@rivosinc.com,
nathan@kernel.org, ndesaulniers@google.com, maskray@google.com,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] riscv: SCS support
Date: Thu, 02 Nov 2023 20:20:30 +0000 [thread overview]
Message-ID: <169895643044.22248.9260509736343720996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230927224757.1154247-8-samitolvanen@google.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Wed, 27 Sep 2023 22:47:58 +0000 you wrote:
> Hi folks,
>
> This series adds Shadow Call Stack (SCS) support for RISC-V. SCS
> uses compiler instrumentation to store return addresses in a
> separate shadow stack to protect them against accidental or
> malicious overwrites. More information about SCS can be found
> here:
>
> [...]
Here is the summary with links:
- [v4,1/6] riscv: VMAP_STACK overflow detection thread-safe
https://git.kernel.org/riscv/c/be97d0db5f44
- [v4,2/6] riscv: Deduplicate IRQ stack switching
https://git.kernel.org/riscv/c/82982fdd5133
- [v4,3/6] riscv: Move global pointer loading to a macro
https://git.kernel.org/riscv/c/e609b4f4252a
- [v4,4/6] riscv: Implement Shadow Call Stack
https://git.kernel.org/riscv/c/d1584d791a29
- [v4,5/6] riscv: Use separate IRQ shadow call stacks
https://git.kernel.org/riscv/c/c40fef858d00
- [v4,6/6] lkdtm: Fix CFI_BACKWARD on RISC-V
https://git.kernel.org/riscv/c/245561ba6d5d
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:[~2023-11-02 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 22:47 [PATCH v4 0/6] riscv: SCS support Sami Tolvanen
2023-09-27 22:47 ` [PATCH v4 1/6] riscv: VMAP_STACK overflow detection thread-safe Sami Tolvanen
2023-09-27 22:48 ` [PATCH v4 2/6] riscv: Deduplicate IRQ stack switching Sami Tolvanen
2023-09-27 22:48 ` [PATCH v4 3/6] riscv: Move global pointer loading to a macro Sami Tolvanen
2023-09-27 22:48 ` [PATCH v4 4/6] riscv: Implement Shadow Call Stack Sami Tolvanen
2023-09-27 22:48 ` [PATCH v4 5/6] riscv: Use separate IRQ shadow call stacks Sami Tolvanen
2023-09-27 22:48 ` [PATCH v4 6/6] lkdtm: Fix CFI_BACKWARD on RISC-V Sami Tolvanen
2023-11-02 20:20 ` 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=169895643044.22248.9260509736343720996.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=cleger@rivosinc.com \
--cc=debug@rivosinc.com \
--cc=guoren@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=maskray@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samitolvanen@google.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