[PATCH] [RFC][PR102768] aarch64: Add compiler support for Shadow Call Stack
Tue Nov 23 08:32:48 GMT 2021
First of all, apologies for my late reply (since I just had a new baby,
I'm quite busy recently and also because I'm not familiar with C++
exception handling, it takes me some time to learn this part).
On 11/3/21 8:00 PM, Szabolcs Nagy wrote:
> The 11/03/2021 00:24, Dan Li wrote:
>> On 11/2/21 9:04 PM, Szabolcs Nagy wrote:
>>> The 11/02/2021 00:06, Dan Li via Gcc-patches wrote:
>>>> Shadow Call Stack can be used to protect the return address of a
>>>> function at runtime, and clang already supports this feature.
>>>> To enable SCS in user mode, in addition to compiler, other support
>>>> is also required (as described in ). This patch only adds basic
>>>> support for SCS from the compiler side, and provides convenience
>>>> for users to enable SCS.
>>>> For linux kernel, only the support of the compiler is required.
>>>>  https://clang.llvm.org/docs/ShadowCallStack.html
>>>>  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102768
>>> i'm not a gcc maintainer, but i prefer such feature
>>> to be in upstream gcc instead of in a plugin.
>>> it will require update to the documentation:
>>> which should mention that it depends on -ffixed-x18
>>> (probably that should be enforced too) which is an
>>> important abi issue: functions following the normal
>>> pcs can clobber x18 and break scs.
>> Thanks Szabolcs, I will update the documentation in next version.
>> It sounds reasonable to enforced -ffixed-x18 with scs, but I see
>> that clang doesn’t do that. Maybe it is better to be consistent
>> with clang here?
> i mean gcc can issue a diagnostic if -ffixed-x18 is not passed.
> (it seems clang rejects scs too without -ffixed-x18)
Oh, yes, you are right. Clang rejects scs without -ffixed-x18,
I should add a similar check in next version.
>>> and that there is no unwinder support.
>> Ok, let me try to add a support for this.
> i assume exception handling info has to change for scs to
> work (to pop the shadow stack when transferring control),
> so either scs must require -fno-exceptions or the eh info
> changes must be implemented.
> i think the kernel does not require exceptions and does
> not depend on the unwinder runtime in libgcc, so this
> is optional for the linux kernel use-case.
I recompiled a glibc and gcc runtime library with -ffixed-x18 enabled.
As you said, the scs stack needs to be popped at the same time during
I saw that Clang is processed by adding
".cfi_escape 0x16, 0x12, 0x02, 0x82, 0x78"
directive (x18 -= 8;) after each emit of scs push.
But this directive has problems when executed in libgcc:
1)context->reg[x] in uw_init_context_1 are all based on cfa, most
registers have no initial values by default.
2)Address of shadow call stack (x18) cannot(and should not) be calculated
based on cfa, and I did not yet find a way to assign hardware register
x18 to context->reg.
3)This causes libgcc to crash when parsing .cfi_escape exp because of 0
address dereference (* x18)
(execute_stack_op => case DW_OP_breg18: _Unwind_GetGR)
4)uw_install_context_1 does not restore all hardware registers by default
before eh return, so context->reg can't write directly to hw x18.
(In clang, __unw_getcontext/__unw_resume will save/restore all hardware
registers, so this directive works fine in my libunwind test.)
I tried to fix this problem through a patch, the exception handling
works fine in my test environment, but I'm not sure if this fix is
ppropriate for two reasons:
1)libgcc does not push/pop all registers by default during exception
handling. Is this change appropriate?
2)The test case may not be able to test this patch, because the test
environment requires at least on glibc/gcc runtime compiled with
May be it's better to rely on -fno-exceptions for this patch first? and If
the glibc/gcc runtime also supports SCS later, the problem can be fixed
at the same time.
I'm still not familiar enough with exception handling in libgcc/libunwind,
please correct me if there are any mistakes :)
More information about the Gcc-patches