From: patchwork-bot+linux-riscv@kernel.org
To: Song Shuai <songshuaishuai@tinylab.org>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, keescook@chromium.org,
guoren@kernel.org, bjorn@rivosinc.com, jszhang@kernel.org,
conor.dooley@microchip.com, andy.chiu@sifive.com,
samitolvanen@google.com, coelacanthushex@gmail.com,
dlemoal@kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, palmer@rivosinc.com
Subject: Re: [PATCH V2] riscv: Support RANDOMIZE_KSTACK_OFFSET
Date: Thu, 25 Jan 2024 21:30:29 +0000 [thread overview]
Message-ID: <170621822937.6239.4360145858676634125.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231109133751.212079-1-songshuaishuai@tinylab.org>
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Thu, 9 Nov 2023 21:37:51 +0800 you wrote:
> Inspired from arm64's implement -- commit 70918779aec9
> ("arm64: entry: Enable random_kstack_offset support")
>
> Add support of kernel stack offset randomization while handling syscall,
> the offset is defaultly limited by KSTACK_OFFSET_MAX() (i.e. 10 bits).
>
> In order to avoid trigger stack canaries (due to __builtin_alloca) and
> slowing down the entry path, use __no_stack_protector attribute to
> disable stack protector for do_trap_ecall_u() at the function level.
>
> [...]
Here is the summary with links:
- [V2] riscv: Support RANDOMIZE_KSTACK_OFFSET
https://git.kernel.org/riscv/c/05d450aabd73
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:[~2024-01-25 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 13:37 [PATCH V2] riscv: Support RANDOMIZE_KSTACK_OFFSET Song Shuai
2024-01-19 10:34 ` Song Shuai
2024-01-25 21:30 ` 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=170621822937.6239.4360145858676634125.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=coelacanthushex@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=dlemoal@kernel.org \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=samitolvanen@google.com \
--cc=songshuaishuai@tinylab.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