From: Mark Rutland <mark.rutland@arm.com>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Kees Cook <keescook@chromium.org>,
Alexander Popov <alex.popov@linux.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] s390/stackleak: provide fast __stackleak_poison() implementation
Date: Wed, 12 Apr 2023 10:02:15 +0100 [thread overview]
Message-ID: <ZDZzl3wAH3zszTqu@FVFF77S0Q05N> (raw)
In-Reply-To: <20230405130841.1350565-3-hca@linux.ibm.com>
On Wed, Apr 05, 2023 at 03:08:41PM +0200, Heiko Carstens wrote:
> Provide an s390 specific __stackleak_poison() implementation which is
> faster than the generic variant.
>
> For the original implementation with an enforced 4kb stackframe for the
> getpid() system call the system call overhead increases by a factor of 3 if
> the stackleak feature is enabled. Using the s390 mvc based variant this is
> reduced to an increase of 25% instead.
>
> This is within the expected area, since the mvc based implementation is
> more or less a memset64() variant which comes with similar results. See
> commit 0b77d6701cf8 ("s390: implement memset16, memset32 & memset64").
With that in mind, could we use memset64() directly (if we made it
noninstr-safe)?
Mark.
>
> Reviewed-by: Vasily Gorbik <gor@linux.ibm.com>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> ---
> arch/s390/include/asm/processor.h | 35 +++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/arch/s390/include/asm/processor.h b/arch/s390/include/asm/processor.h
> index efffc28cbad8..dc17896a001a 100644
> --- a/arch/s390/include/asm/processor.h
> +++ b/arch/s390/include/asm/processor.h
> @@ -118,6 +118,41 @@ unsigned long vdso_size(void);
>
> #define HAVE_ARCH_PICK_MMAP_LAYOUT
>
> +#define __stackleak_poison __stackleak_poison
> +static __always_inline void __stackleak_poison(unsigned long erase_low,
> + unsigned long erase_high,
> + unsigned long poison)
> +{
> + unsigned long tmp, count;
> +
> + count = erase_high - erase_low;
> + if (!count)
> + return;
> + asm volatile(
> + " cghi %[count],8\n"
> + " je 2f\n"
> + " aghi %[count],-(8+1)\n"
> + " srlg %[tmp],%[count],8\n"
> + " ltgr %[tmp],%[tmp]\n"
> + " jz 1f\n"
> + "0: stg %[poison],0(%[addr])\n"
> + " mvc 8(256-8,%[addr]),0(%[addr])\n"
> + " la %[addr],256(%[addr])\n"
> + " brctg %[tmp],0b\n"
> + "1: stg %[poison],0(%[addr])\n"
> + " larl %[tmp],3f\n"
> + " ex %[count],0(%[tmp])\n"
> + " j 4f\n"
> + "2: stg %[poison],0(%[addr])\n"
> + " j 4f\n"
> + "3: mvc 8(1,%[addr]),0(%[addr])\n"
> + "4:\n"
> + : [addr] "+&a" (erase_low), [count] "+&d" (count), [tmp] "=&a" (tmp)
> + : [poison] "d" (poison)
> + : "memory", "cc"
> + );
> +}
> +
> /*
> * Thread structure
> */
> --
> 2.37.2
>
next prev parent reply other threads:[~2023-04-12 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 13:08 [PATCH 0/2] stackleak: allow to specify arch specific stackleak poison function Heiko Carstens
2023-04-05 13:08 ` [PATCH 1/2] " 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 [this message]
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=ZDZzl3wAH3zszTqu@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=alex.popov@linux.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®