From: patchwork-bot+linux-riscv@kernel.org
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: linux-riscv@lists.infradead.org, catalin.marinas@arm.com,
will@kernel.org, chenhuacai@kernel.org, maddy@linux.ibm.com,
mpe@ellerman.id.au, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, kees@kernel.org,
gustavoars@kernel.org, arnd@arndb.de, mark.rutland@arm.com,
Jason@zx2c4.com, ardb@kernel.org, jeremy.linton@arm.com,
david.laight.linux@gmail.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH v5 0/2] Fix bugs and performance of kstack offset randomisation
Date: Thu, 30 Apr 2026 03:25:28 +0000 [thread overview]
Message-ID: <177751952875.2274119.16398594062786998071.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260303150840.3789438-1-ryan.roberts@arm.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Kees Cook <kees@kernel.org>:
On Tue, 3 Mar 2026 15:08:37 +0000 you wrote:
> [Kees; I'm hoping this is now good-to-go via your hardening tree? It would be
> good to get some linux-next testing.]
>
> Hi All,
>
> As I reported at [1], kstack offset randomisation suffers from a couple of bugs
> and, on arm64 at least, the performance is poor. This series attempts to fix
> both; patch 1 provides back-portable fixes for the functional bugs. Patch 2
> proposes a performance improvement approach.
>
> [...]
Here is the summary with links:
- [v5,1/2] randomize_kstack: Maintain kstack_offset per task
https://git.kernel.org/riscv/c/37beb4256016
- [v5,2/2] randomize_kstack: Unify random source across arches
https://git.kernel.org/riscv/c/a96ef5848cb0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-30 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 15:08 [PATCH v5 0/2] Fix bugs and performance of kstack offset randomisation Ryan Roberts
2026-03-03 15:08 ` [PATCH v5 1/2] randomize_kstack: Maintain kstack_offset per task Ryan Roberts
2026-03-03 15:08 ` [PATCH v5 2/2] randomize_kstack: Unify random source across arches Ryan Roberts
2026-03-11 8:32 ` [PATCH v5 0/2] Fix bugs and performance of kstack offset randomisation Ryan Roberts
2026-03-25 4:14 ` Kees Cook
2026-04-30 3:25 ` 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=177751952875.2274119.16398594062786998071.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Jason@zx2c4.com \
--cc=agordeev@linux.ibm.com \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=david.laight.linux@gmail.com \
--cc=gor@linux.ibm.com \
--cc=gustavoars@kernel.org \
--cc=hca@linux.ibm.com \
--cc=jeremy.linton@arm.com \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=tglx@linutronix.de \
--cc=will@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