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,
nathan@kernel.org, ndesaulniers@google.com,
conor.dooley@microchip.com, llvm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] riscv: KCFI support
Date: Wed, 30 Aug 2023 13:20:34 +0000 [thread overview]
Message-ID: <169340163454.19859.5631159121933404323.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230710183544.999540-8-samitolvanen@google.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Mon, 10 Jul 2023 18:35:45 +0000 you wrote:
> This series adds KCFI support for RISC-V. KCFI is a fine-grained
> forward-edge control-flow integrity scheme supported in Clang >=16,
> which ensures indirect calls in instrumented code can only branch to
> functions whose type matches the function pointer type, thus making
> code reuse attacks more difficult.
>
> Patch 1 implements a pt_regs based syscall wrapper to address
> function pointer type mismatches in syscall handling. Patches 2 and 3
> annotate indirectly called assembly functions with CFI types. Patch 4
> implements error handling for indirect call checks. Patch 5 disables
> CFI for arch/riscv/purgatory. Patch 6 finally allows CONFIG_CFI_CLANG
> to be enabled for RISC-V.
>
> [...]
Here is the summary with links:
- [v2,1/6] riscv: Implement syscall wrappers
https://git.kernel.org/riscv/c/08d0ce30e0e4
- [v2,2/6] riscv: Add types to indirectly called assembly functions
https://git.kernel.org/riscv/c/5f59c6855bad
- [v2,3/6] riscv: Add ftrace_stub_graph
https://git.kernel.org/riscv/c/f3a0c23f2539
- [v2,4/6] riscv: Add CFI error handling
https://git.kernel.org/riscv/c/af0ead42f693
- [v2,5/6] riscv/purgatory: Disable CFI
https://git.kernel.org/riscv/c/a72ab0361110
- [v2,6/6] riscv: Allow CONFIG_CFI_CLANG to be selected
https://git.kernel.org/riscv/c/74f8fc31feb4
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-08-30 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 18:35 [PATCH v2 0/6] riscv: KCFI support Sami Tolvanen
2023-07-10 18:35 ` [PATCH v2 1/6] riscv: Implement syscall wrappers Sami Tolvanen
2023-07-10 18:35 ` [PATCH v2 2/6] riscv: Add types to indirectly called assembly functions Sami Tolvanen
2023-07-10 18:35 ` [PATCH v2 3/6] riscv: Add ftrace_stub_graph Sami Tolvanen
2023-07-10 18:35 ` [PATCH v2 4/6] riscv: Add CFI error handling Sami Tolvanen
2023-07-10 18:35 ` [PATCH v2 5/6] riscv/purgatory: Disable CFI Sami Tolvanen
2023-07-10 18:35 ` [PATCH v2 6/6] riscv: Allow CONFIG_CFI_CLANG to be selected Sami Tolvanen
2023-07-10 19:08 ` [PATCH v2 0/6] riscv: KCFI support Palmer Dabbelt
2023-08-30 13: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=169340163454.19859.5631159121933404323.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--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