Lines Matching full:will

47 * GCS specific errors (those reported with EC 0x2d) will be reported as
56   in LR match those in the GCS, the LR will be ignored.  This is not supported
78 * Any unknown flags will cause PR_SET_SHADOW_STACK_STATUS to return -EINVAL.
82   status of the specified GCS mode bits will be rejected.
91   thread that called them, any other running threads will be unaffected.
102   the stack will remain allocated for the lifetime of the thread.  At present
103   any attempt to reenable GCS for the thread will be rejected, this may be
106 * It should be noted that since enabling GCS will result in GCS becoming
109   usage will be that GCS is enabled very early in execution of a program.
116 * When GCS is enabled for a thread a new Guarded Control Stack will be
121   new Guarded Control Stack will be allocated for the new thread with
125   the top 8 bytes of the stack will be initialised to 0 and GCSPR_EL0 will
134   SHADOW_STACK_SET_TOKEN is specified a cap will be placed on the stack,
135   if SHADOW_STACK_SET_MARKER is not specified the cap will be the top 8
136   bytes of the stack and if it is specified then the cap will be the next
147   that thread will be freed.  Note carefully that if the stack has been
155   pointer for the interrupted context on signal delivery.  This will always
165   GCS cap token will be written to the GCS, this is an architectural GCS cap
167   signal frame will point to this cap token.
169 * The signal handler will use the same GCS as the interrupted context.
172   return handler will be pushed onto the GCS, allowing return from the signal
173   handler via RET as normal.  This will not be reported in the gcs_context in
183   and GCSPR_EL0 will be restored from that context prior to further
187   configuration will be unchanged.
190   point to a valid GCS signal cap record, this will be popped from the
194   attempt to change the GCS configuration will be treated as an error.  This
198   signal return will be rejected.
208   If GCS is enabled via ptrace no new GCS will be allocated for the thread.
216 * NT_ARM_GCS notes will be added to each coredump for each thread of the
217   dumped process.  The contents will be equivalent to the data that would
226 * Guarded Control Stack pages will include "ss" in their VmFlags in