From: Dan Li <ashimida@linux.alibaba.com>
To: Ard Biesheuvel <ardb@kernel.org>,
gcc-patches@gcc.gnu.org,
Richard Earnshaw <richard.earnshaw@arm.com>,
marcus.shawcroft@arm.com, Kyrylo Tkachov <kyrylo.tkachov@arm.com>,
hp@gcc.gnu.org, Nick Desaulniers <ndesaulniers@google.com>,
nsz@gcc.gnu.org, pageexec@gmail.com, qinzhao@gcc.gnu.org,
linux-hardening@vger.kernel.org,
Peter Collingbourne <pcc@google.com>,
Sami Tolvanen <samitolvanen@google.com>,
Kees Cook <keescook@chromium.org>,
richard.sandiford@arm.com
Subject: Re: [PING^3][PATCH,v2,1/1,AARCH64][PR102768] aarch64: Add compiler support for Shadow Call Stack
Date: Wed, 2 Feb 2022 01:25:33 -0800 [thread overview]
Message-ID: <7adf6644-55ce-d90e-2f62-66792364d337@linux.alibaba.com> (raw)
In-Reply-To: <mptfsp3lvm5.fsf@arm.com>
On 1/31/22 08:26, Richard Sandiford wrote:
> Thanks for the discussion and sorry for the slow reply, was out most of
> last week.
>
> Dan Li <ashimida@linux.alibaba.com> writes:
>> Thanks, Ard,
>>
>> On 1/26/22 00:10, Ard Biesheuvel wrote:
>>> On Wed, 26 Jan 2022 at 08:53, Dan Li <ashimida@linux.alibaba.com> wrote:
>>>>
>>>> Hi, all,
>>>>
>>>> Sorry for bothering.
>>>>
>>>> I'm trying to commit aarch64 scs code to the gcc and there is an issue
>>>> that I'm not sure about, could someone give me some suggestions?
>>>> (To avoid noise, I did't cc PING^3 [1] to the kernel mail list :) )
>>>>
>>> So omitting the load of X30 from the ordinary stack seems fine to me.
>
> OK, thanks. Let's go with that for now then. There would still be
> time to change our minds before GCC 12 is released, if anyone feels
> that patching SCS code would be useful.
>> Reading it back, I think my previous message came across as sounding
> like a complaint against binary patching, which wasn't the case at all.
> I think it would be fine to support patching, even if it was just for a
> single vendor rather than expected to be a common case. It's just that,
> if we did want to support it, we'd need to document it as a requirement
> (at least within GCC) and change the implementation accordingly.
>
Got it, then I'll implement this feature as discussed above and see
if we could add additional options for SCS later.
Thanks,
Dan
prev parent reply other threads:[~2022-02-02 9:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 7:06 [PATCH] [RFC][PR102768] aarch64: Add compiler support for Shadow Call Stack Dan Li
2021-11-02 13:04 ` Szabolcs Nagy
2021-11-02 16:24 ` Dan Li
2021-11-03 12:00 ` Szabolcs Nagy
2021-11-23 8:32 ` Dan Li
2021-11-23 10:51 ` Szabolcs Nagy
2021-11-23 13:39 ` Dan Li
2021-12-06 2:41 ` [PATCH] [PATCH,v2,1/1,AARCH64][PR102768] " Dan Li
2021-12-06 3:22 ` Dan Li
2022-01-04 14:40 ` [PING^2][PATCH,v2,1/1,AARCH64][PR102768] " Dan Li
[not found] ` <81d54b71-7c9c-47ef-ac8d-72aae46cd4ee@linux.alibaba.com>
[not found] ` <mptk0euk42w.fsf@arm.com>
[not found] ` <a9daf6bf-94f2-0c5f-b9aa-7fb69781c9d5@linux.alibaba.com>
[not found] ` <mpto840kti9.fsf@arm.com>
[not found] ` <3ae4a533-352b-f3e3-27b3-9386df5f56c3@linux.alibaba.com>
2022-01-26 7:53 ` [PING^3][PATCH,v2,1/1,AARCH64][PR102768] " Dan Li
2022-01-26 8:10 ` Ard Biesheuvel
2022-01-26 10:35 ` Dan Li
2022-01-26 11:09 ` Ard Biesheuvel
2022-01-26 14:08 ` Dan Li
2022-01-31 16:26 ` Richard Sandiford
2022-02-02 9:25 ` Dan Li [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=7adf6644-55ce-d90e-2f62-66792364d337@linux.alibaba.com \
--to=ashimida@linux.alibaba.com \
--cc=ardb@kernel.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@gcc.gnu.org \
--cc=keescook@chromium.org \
--cc=kyrylo.tkachov@arm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=marcus.shawcroft@arm.com \
--cc=ndesaulniers@google.com \
--cc=nsz@gcc.gnu.org \
--cc=pageexec@gmail.com \
--cc=pcc@google.com \
--cc=qinzhao@gcc.gnu.org \
--cc=richard.earnshaw@arm.com \
--cc=richard.sandiford@arm.com \
--cc=samitolvanen@google.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;
as well as URLs for NNTP newsgroup(s).