From: Paul Walmsley <pjw@kernel.org>
To: Deepak Gupta <debug@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, akpm@linux-foundation.org,
Liam.Howlett@oracle.com, vbabka@suse.cz,
lorenzo.stoakes@oracle.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, conor@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, arnd@arndb.de,
brauner@kernel.org, peterz@infradead.org, oleg@redhat.com,
ebiederm@xmission.com, kees@kernel.org, corbet@lwn.net,
shuah@kernel.org, jannh@google.com, conor+dt@kernel.org,
ojeda@kernel.org, alex.gaynor@gmail.com, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
lossin@kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
devicetree@vger.kernel.org, linux-arch@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
alistair.francis@wdc.com, richard.henderson@linaro.org,
jim.shu@sifive.com, andybnac@gmail.com, kito.cheng@sifive.com,
charlie@rivosinc.com, atishp@rivosinc.com, evan@rivosinc.com,
cleger@rivosinc.com, alexghiti@rivosinc.com,
samitolvanen@google.com, broonie@kernel.org,
rick.p.edgecombe@intel.com, rust-for-linux@vger.kernel.org,
zong.li@sifive.com, david@redhat.com,
andreas.korb@aisec.fraunhofer.de,
valentin.haudiquet@canonical.com, cmirabil@redhat.com
Subject: Re: [PATCH v26 00/28] riscv control-flow integrity for usermode
Date: Fri, 12 Dec 2025 01:15:11 -0700 (MST) [thread overview]
Message-ID: <b9991702-44d9-1f0d-e5c8-677c404e2522@kernel.org> (raw)
In-Reply-To: <176551861579.2032148.13920544388182691102.git-patchwork-notify@kernel.org>
On Fri, 12 Dec 2025, patchwork-bot+linux-riscv@kernel.org wrote:
> This series was applied to riscv/linux.git (for-next)
> by Paul Walmsley <pjw@kernel.org>:
>
> On Thu, 11 Dec 2025 09:20:33 -0800 you wrote:
> > v26: CONFIG_RISCV_USER_CFI depends on CONFIG_MMU (dependency of shadow stack
> > on MMU). Used b4 to pick tags, apparantly it messed up some tag picks. Fixing it
This is the Patchwork bot getting things wrong, again.
What got repushed was a slightly modified version of the v23 series --
with the non-code changes described here:
https://lore.kernel.org/linux-riscv/176551861579.2032148.13920544388182691102.git-patchwork-notify@kernel.org/T/#t
Deepak: as others have pointed out, you shouldn't be sending patch series
during merge windows.
- Paul
next prev parent reply other threads:[~2025-12-12 8:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 17:20 [PATCH v26 00/28] riscv control-flow integrity for usermode Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 01/28] mm: VM_SHADOW_STACK definition for riscv Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 02/28] dt-bindings: riscv: zicfilp and zicfiss in dt-bindings (extensions.yaml) Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 03/28] riscv: zicfiss / zicfilp enumeration Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 04/28] riscv: zicfiss / zicfilp extension csr and bit definitions Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 05/28] riscv: usercfi state for task and save/restore of CSR_SSP on trap entry/exit Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 06/28] riscv/mm : ensure PROT_WRITE leads to VM_READ | VM_WRITE Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 07/28] riscv/mm: manufacture shadow stack pte Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 08/28] riscv/mm: teach pte_mkwrite to manufacture shadow stack PTEs Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 09/28] riscv/mm: write protect and shadow stack Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 10/28] riscv/mm: Implement map_shadow_stack() syscall Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 11/28] riscv/shstk: If needed allocate a new shadow stack on clone Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 12/28] riscv: Implements arch agnostic shadow stack prctls Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 13/28] prctl: arch-agnostic prctl for indirect branch tracking Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 14/28] riscv: Implements arch agnostic indirect branch tracking prctls Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 15/28] riscv/traps: Introduce software check exception and uprobe handling Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 16/28] riscv: signal: abstract header saving for setup_sigcontext Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 17/28] riscv/signal: save and restore of shadow stack for signal Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 18/28] riscv/kernel: update __show_regs to print shadow stack register Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 19/28] riscv/ptrace: riscv cfi status and state via ptrace and in core files Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 20/28] riscv/hwprobe: zicfilp / zicfiss enumeration in hwprobe Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 21/28] riscv: kernel command line option to opt out of user cfi Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 22/28] riscv: enable kernel access to shadow stack memory via FWFT sbi call Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 23/28] arch/riscv: compile vdso with landing pad and shadow stack note Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 24/28] arch/riscv: dual vdso creation logic and select vdso based on hw Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 25/28] riscv: create a config for shadow stack and landing pad instr support Deepak Gupta via B4 Relay
2025-12-11 17:20 ` [PATCH v26 26/28] riscv: Documentation for landing pad / indirect branch tracking Deepak Gupta via B4 Relay
2025-12-11 17:21 ` [PATCH v26 27/28] riscv: Documentation for shadow stack on riscv Deepak Gupta via B4 Relay
2025-12-11 17:21 ` [PATCH v26 28/28] kselftest/riscv: kselftest for user mode cfi Deepak Gupta via B4 Relay
2025-12-12 5:50 ` [PATCH v26 00/28] riscv control-flow integrity for usermode patchwork-bot+linux-riscv
2025-12-12 8:15 ` Paul Walmsley [this message]
2025-12-12 8:30 ` Paul Walmsley
2025-12-12 18:33 ` Deepak Gupta
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=b9991702-44d9-1f0d-e5c8-677c404e2522@kernel.org \
--to=pjw@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=alexghiti@rivosinc.com \
--cc=aliceryhl@google.com \
--cc=alistair.francis@wdc.com \
--cc=andreas.korb@aisec.fraunhofer.de \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=atishp@rivosinc.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=cmirabil@redhat.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=debug@rivosinc.com \
--cc=devicetree@vger.kernel.org \
--cc=ebiederm@xmission.com \
--cc=evan@rivosinc.com \
--cc=gary@garyguo.net \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=jim.shu@sifive.com \
--cc=kees@kernel.org \
--cc=kito.cheng@sifive.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lossin@kernel.org \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=richard.henderson@linaro.org \
--cc=rick.p.edgecombe@intel.com \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=valentin.haudiquet@canonical.com \
--cc=vbabka@suse.cz \
--cc=x86@kernel.org \
--cc=zong.li@sifive.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;
as well as URLs for NNTP newsgroup(s).