From: Peter Zijlstra <peterz@infradead.org>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Cc: "Torvalds, Linus" <torvalds@linux-foundation.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"fweimer@redhat.com" <fweimer@redhat.com>,
"hjl.tools@gmail.com" <hjl.tools@gmail.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: CET shadow stack app compatibility
Date: Tue, 15 Nov 2022 19:45:03 +0100 [thread overview]
Message-ID: <Y3PeLxWstXnMlB1u@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <883ed1a3f4de8d508c4bc2f504ae4a5c8db19a20.camel@intel.com>
On Tue, Nov 15, 2022 at 05:04:40PM +0000, Edgecombe, Rick P wrote:
> > ELF bits should not, must not, be called CET. API, not CET, Compiler
> > features, also not CET.
>
> So the arch_prctl()s can't be shared between shadow stack and IBT? They
> don't have to be, but this is a new thing after a fair amount of
> earlier discussion.
I would very strongly suggest IBT not use that interface and instead we
follow ARM64 BTI's lead -- such that application developers don't go
insane trying to use two nearly identical solutions.
I mean, the toolchain folks made a godawefull mess of things, but we
don't have to.
prev parent reply other threads:[~2022-11-15 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 23:15 CET shadow stack app compatibility Edgecombe, Rick P
2022-11-15 2:01 ` Linus Torvalds
2022-11-15 7:33 ` Florian Weimer
2022-11-15 16:57 ` Edgecombe, Rick P
2022-12-02 18:48 ` Florian Weimer
2022-12-05 19:02 ` Edgecombe, Rick P
2022-11-15 9:43 ` Peter Zijlstra
2022-11-15 17:04 ` Edgecombe, Rick P
2022-11-15 18:45 ` Peter Zijlstra [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=Y3PeLxWstXnMlB1u@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=torvalds@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).