public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Paul Walmsley <pjw@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, tglx@linutronix.de,
	peterz@infradead.org, broonie@kernel.org
Subject: Re: [PATCH 0/6] Restructure per-task CFI prctl() and ptrace interfaces
Date: Sat, 04 Apr 2026 01:50:10 +0000	[thread overview]
Message-ID: <177526741054.1520684.8289044721186928310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <177526680875.878386.16551569883089050686.stgit@seppa>

Hello:

This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.org>:

On Fri,  3 Apr 2026 19:40:56 -0600 you wrote:
> Restructure the per-task CFI indirect branch landing pad prctl()
> interface, as suggested by Linus [1].  In place of the current
> approach, which follows the style of shadow stack control prctl()s
> (PR_{GET,SET,LOCK}_SHADOW_STACK_STATUS), adopt the style of the
> speculation control prctl() constants (PR_{GET,SET}_SPECULATION_CTRL).
> 
> Then, to improve readability, expand "indir_br_lp", "lpad", and
> related abbreviations in the interfaces, also as requested by Linus.
> While here, expand "ss" in the shadow stack ptrace macros to "shadow
> stack".
> 
> [...]

Here is the summary with links:
  - [1/6] riscv: ptrace: cfi: fix "PRACE" typo in uapi header
    (no matching commit)
  - [2/6] riscv: cfi: clear CFI lock status in start_thread()
    (no matching commit)
  - [3/6] riscv: ptrace: expand "LP" references to "branch landing pads" in uapi headers
    (no matching commit)
  - [4/6] prctl: rename branch landing pad implementation functions to be more explicit
    https://git.kernel.org/riscv/c/987bd38dee75
  - [5/6] riscv: ptrace: cfi: expand "SS" references to "shadow stack" in uapi headers
    https://git.kernel.org/riscv/c/c8acc707f48c
  - [6/6] prctl: cfi: change the branch landing pad prctl()s to be more descriptive
    https://git.kernel.org/riscv/c/e0d96d3c63f5

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

  parent reply	other threads:[~2026-04-04  1:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-04  1:40 [PATCH 0/6] Restructure per-task CFI prctl() and ptrace interfaces Paul Walmsley
2026-04-04  1:41 ` [PATCH 1/6] riscv: ptrace: cfi: fix "PRACE" typo in uapi header Paul Walmsley
2026-04-04  1:41 ` [PATCH 2/6] riscv: cfi: clear CFI lock status in start_thread() Paul Walmsley
2026-04-04  1:41 ` [PATCH 3/6] riscv: ptrace: expand "LP" references to "branch landing pads" in uapi headers Paul Walmsley
2026-04-04  1:41 ` [PATCH 4/6] prctl: rename branch landing pad implementation functions to be more explicit Paul Walmsley
2026-04-04  1:41 ` [PATCH 5/6] riscv: ptrace: cfi: expand "SS" references to "shadow stack" in uapi headers Paul Walmsley
2026-04-04  1:41 ` [PATCH 6/6] prctl: cfi: change the branch landing pad prctl()s to be more descriptive Paul Walmsley
2026-04-04  1:50 ` patchwork-bot+linux-riscv [this message]
2026-04-05  0:50 ` [PATCH 0/6] Restructure per-task CFI prctl() and ptrace interfaces patchwork-bot+linux-riscv

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=177526741054.1520684.8289044721186928310.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=peterz@infradead.org \
    --cc=pjw@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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