From: Dave Hansen <dave.hansen@intel.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Rick P Edgecombe <rick.p.edgecombe@intel.com>
Subject: Re: [PATCH] x86/shstk: Enable shadow stack for x32
Date: Fri, 22 Mar 2024 09:56:35 -0700 [thread overview]
Message-ID: <ece5cc63-960d-4323-9128-5023b6d94dc0@intel.com> (raw)
In-Reply-To: <CAMe9rOrZ8XDoeDru+zm1ad7NsLHgkD1cm=CL==uhWY4OqqQGJg@mail.gmail.com>
On 3/22/24 09:52, H.J. Lu wrote:
> On Fri, Mar 22, 2024 at 9:49 AM Dave Hansen <dave.hansen@intel.com> wrote:
>> On 3/15/24 07:04, H.J. Lu wrote:
>>> 1. Add shadow stack support to x32 signal.
>>> 2. Use the 64-bit map_shadow_stack syscall for x32.
>>> 3. Set up shadow stack for x32.
>>>
>>> Tested with shadow stack enabled x32 glibc on Intel Tiger Lake.
>> I don't think we should wire up code that's never going to get used in
>> practice. I think I'd want to be sure of the existence of some
>> specific, real-world, long-term users of this before we add a new ABI
>> that we need to support forever.
>>
>> Are there real users?
> Were you talking about x32 users or x32 users with shadow stack?
x32 users who both want and will use shadow stacks.
It's been a long time since I've seen an x32 bug report.
next prev parent reply other threads:[~2024-03-22 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 14:04 H.J. Lu
2024-03-15 14:20 ` Edgecombe, Rick P
2024-03-15 14:34 ` H.J. Lu
2024-03-22 14:07 ` Edgecombe, Rick P
2024-03-22 14:28 ` Edgecombe, Rick P
2024-03-22 15:06 ` H.J. Lu
2024-03-22 15:58 ` Edgecombe, Rick P
2024-03-22 16:07 ` H.J. Lu
2024-03-22 16:21 ` Edgecombe, Rick P
2024-03-22 16:35 ` H.J. Lu
2024-03-22 10:59 ` [tip: x86/shstk] x86/shstk: Enable shadow stacks " tip-bot2 for H.J. Lu
2024-03-22 16:49 ` Borislav Petkov
2024-03-22 16:49 ` [PATCH] x86/shstk: Enable shadow stack " Dave Hansen
2024-03-22 16:52 ` H.J. Lu
2024-03-22 16:56 ` Dave Hansen [this message]
2024-03-22 17:00 ` H.J. Lu
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=ece5cc63-960d-4323-9128-5023b6d94dc0@intel.com \
--to=dave.hansen@intel.com \
--cc=hjl.tools@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.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
all inboxes | Powered by JetHome®