public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fangfei Yang <yangff1@gmail.com>
To: luto@kernel.org
Cc: dave.hansen@intel.com, dave.hansen@linux.intel.com,
	keescook@chromium.org, linux-kernel@vger.kernel.org,
	sroettger@google.com, x86@kernel.org
Subject: Re: PKU usage improvements for threads
Date: Fri,  2 Sep 2022 19:16:48 -0500	[thread overview]
Message-ID: <20220903001648.17171-1-yangff1@gmail.com> (raw)
In-Reply-To: <26078f2a-67be-4aa1-bbb2-dcd1168c9d12@www.fastmail.com>

> sys_sigaltstack() is already pretty much useless with SHSTK, and it’s kinda busted with AVX512. How about we just add a whole new non-kludgy API?

Hi, why is that useless? Signal is not going to change the SSP, all it needs to do is creating a token that can be restored by sigreturn in the future on the current shadow stack.
Can you provide some examples about that? Thank you.

  parent reply	other threads:[~2022-09-03  0:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 20:40 PKU usage improvements for threads Kees Cook
2022-08-22 21:11 ` Dave Hansen
2022-08-23 11:08   ` Stephen Röttger
2022-08-23 18:12     ` Dave Hansen
2022-08-23 18:24       ` Andy Lutomirski
2022-08-24  8:51         ` Stephen Röttger
2022-08-24 16:28           ` Dave Hansen
2022-08-24 16:45           ` Andy Lutomirski
2022-08-25 12:30             ` Stephen Röttger
2022-08-25 14:36               ` Dave Hansen
2022-09-02 17:18                 ` Andy Lutomirski
2022-09-03  0:16         ` Fangfei Yang [this message]
2022-09-03  0:14       ` Fangfei Yang
2022-09-06  4:34         ` Andy Lutomirski
2022-09-06  5:58           ` Fangfei Yang

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=20220903001648.17171-1-yangff1@gmail.com \
    --to=yangff1@gmail.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=sroettger@google.com \
    --cc=x86@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