Re: [PATCH v2] riscv: cif: clear CFI lock status in start_thread - patchwork-bot+linux-riscv

From: patchwork-bot+linux-riscv@kernel.org
To: Zong Li <zong.li@sifive.com>
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	debug@rivosinc.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: cif: clear CFI lock status in start_thread
Date: Fri, 03 Apr 2026 18:30:19 +0000	[thread overview]
Message-ID: <177524101929.1406513.17935249584196431471.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260323065640.4045713-1-zong.li@sifive.com>

Hello:

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

On Sun, 22 Mar 2026 23:56:40 -0700 you wrote:
> When libc locks the CFI status through the following prctl:
>  - PR_LOCK_SHADOW_STACK_STATUS
>  - PR_LOCK_INDIR_BR_LP_STATUS
> 
> A newly execd address space will inherit the lock status
> if it does not clear the lock bits. Since the lock bits
> remain set, libc will later fail to enable the landing
> pad and shadow stack.
> 
> [...]

Here is the summary with links:
  - [v2] riscv: cif: clear CFI lock status in start_thread
    https://git.kernel.org/riscv/c/b3a20899d255

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