linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Kees Cook <kees@kernel.org>
Cc: linux-riscv@lists.infradead.org, peterz@infradead.org,
	samitolvanen@google.com, dwmw2@infradead.org,
	linus.walleij@linaro.org, mark.rutland@arm.com,
	puranjay@kernel.org, corbet@lwn.net, nathan@kernel.org,
	x86@kernel.org, linux-doc@vger.kernel.org,
	linux-kbuild@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, llvm@lists.linux.dev,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH 0/5] kcfi: Prepare for GCC support
Date: Tue, 14 Oct 2025 01:12:07 +0000	[thread overview]
Message-ID: <176040432799.3390136.12370033021047300981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250825141316.work.967-kees@kernel.org>

Hello:

This series was applied to riscv/linux.git (for-next)
by Peter Zijlstra <peterz@infradead.org>:

On Mon, 25 Aug 2025 07:25:47 -0700 you wrote:
> Hi,
> 
> With KCFI support in GCC coming[1], we need to make some (relatively
> small) changes in the kernel to deal with it:
> 
> - move __nocfi out of compilers-clang.h (so GCC can see it too)
> - add cfi=debug so future Kees can find breakage easier
> - remove problematic __noinitretpoline usage
> - rename CONFIG_CFI_CLANG to CONFIG_CFI (otherwise is it quite confusing)
> 
> [...]

Here is the summary with links:
  - [1/5] compiler_types.h: Move __nocfi out of compiler-specific header
    https://git.kernel.org/riscv/c/038c7dc66e27
  - [2/5] x86/traps: Clarify KCFI instruction layout
    https://git.kernel.org/riscv/c/628a15e0536a
  - [3/5] x86/cfi: Add option for cfi=debug bootparam
    (no matching commit)
  - [4/5] x86/cfi: Remove __noinitretpoline and __noretpoline
    https://git.kernel.org/riscv/c/0b815825b1b0
  - [5/5] kcfi: Rename CONFIG_CFI_CLANG to CONFIG_CFI
    (no matching commit)

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



      parent reply	other threads:[~2025-10-14  1:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 14:25 [PATCH 0/5] kcfi: Prepare for GCC support Kees Cook
2025-08-25 14:25 ` [PATCH 1/5] compiler_types.h: Move __nocfi out of compiler-specific header Kees Cook
2025-08-27 19:46   ` Nathan Chancellor
2025-08-25 14:25 ` [PATCH 2/5] x86/traps: Clarify KCFI instruction layout Kees Cook
2025-08-25 14:25 ` [PATCH 3/5] x86/cfi: Add option for cfi=debug bootparam Kees Cook
2025-08-25 15:34   ` Kees Cook
2025-08-25 15:59   ` Peter Zijlstra
2025-08-25 16:16     ` Kees Cook
2025-08-27 19:57   ` Nathan Chancellor
2025-08-29  1:49     ` Kees Cook
2025-08-25 14:25 ` [PATCH 4/5] x86/cfi: Remove __noinitretpoline and __noretpoline Kees Cook
2025-08-25 14:25 ` [PATCH 5/5] kcfi: Rename CONFIG_CFI_CLANG to CONFIG_CFI Kees Cook
2025-08-25 15:01   ` Miguel Ojeda
2025-08-25 15:35     ` Kees Cook
2025-08-25 17:00       ` Miguel Ojeda
2025-08-25 19:31         ` Kees Cook
2025-08-27  1:34           ` Nathan Chancellor
2025-08-27  7:35             ` Randy Dunlap
2025-08-27 19:38               ` Nathan Chancellor
2025-08-28  6:14                 ` Randy Dunlap
2025-08-28 12:11                 ` Miguel Ojeda
2025-08-28 20:19                   ` Nathan Chancellor
2025-08-28 20:32                     ` Kees Cook
2025-08-28 22:22                       ` Nathan Chancellor
2025-08-28 22:55                       ` Miguel Ojeda
2025-08-28 22:46                     ` Miguel Ojeda
2025-08-26 21:49   ` Jeff Johnson
2025-08-28 12:08   ` Linus Walleij
2025-10-14  1:12 ` 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=176040432799.3390136.12370033021047300981.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dwmw2@infradead.org \
    --cc=kees@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=llvm@lists.linux.dev \
    --cc=mark.rutland@arm.com \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=puranjay@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=x86@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).