From: Heiko Carstens <hca@linux.ibm.com>
To: Kees Cook <keescook@chromium.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Popov <alex.popov@linux.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] stackleak: allow to specify arch specific stackleak poison function
Date: Wed, 5 Apr 2023 15:08:39 +0200 [thread overview]
Message-ID: <20230405130841.1350565-1-hca@linux.ibm.com> (raw)
Factor out the code that fills the stack with the stackleak poison value in
order to allow architectures to provide a faster implementation.
Use this to provide an s390 specific implementation which can fill the
stack with the poison value much faster (factor of ~10 compared to the
current version).
Note that the s390 stackleak support is currently only available via
linux-next (as of today), and the s390 kernel tree at kernel.org[1].
Therefore, if there are no objections, I'd like to add these two patches to
the s390 tree, so they can go upstream via the next merge window together
with the s390 support.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features&id=b94c0ebb1ec752016a3e41bfb66bb51ea905e533
Thanks,
Heiko
Heiko Carstens (2):
stackleak: allow to specify arch specific stackleak poison function
s390/stackleak: provide fast __stackleak_poison() implementation
arch/s390/include/asm/processor.h | 35 +++++++++++++++++++++++++++++++
kernel/stackleak.c | 17 +++++++++++----
2 files changed, 48 insertions(+), 4 deletions(-)
--
2.37.2
next reply other threads:[~2023-04-05 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 13:08 Heiko Carstens [this message]
2023-04-05 13:08 ` [PATCH 1/2] stackleak: allow to specify arch specific stackleak poison function Heiko Carstens
2023-04-12 9:03 ` Mark Rutland
2023-04-12 9:58 ` Heiko Carstens
2023-04-12 10:06 ` Mark Rutland
2023-04-05 13:08 ` [PATCH 2/2] s390/stackleak: provide fast __stackleak_poison() implementation Heiko Carstens
2023-04-12 9:02 ` Mark Rutland
2023-04-18 17:21 ` [PATCH 0/2] stackleak: allow to specify arch specific stackleak poison function Heiko Carstens
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=20230405130841.1350565-1-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=alex.popov@linux.com \
--cc=gor@linux.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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