For userspace checkpoint and restore (C/R) a way of getting process state containing RSEQ configuration is needed. There are two ways this information is going to be used: - to re-enable RSEQ for threads which had it enabled before C/R - to detect if a thread was in a critical section during C/R Since C/R preserves TLS memory and addresses RSEQ ABI will be restored using the address registered before C/R. Detection whether the thread is in a critical section during C/R is needed to enforce behavior of RSEQ abort during C/R. Attaching with ptrace() before registers are dumped itself doesn't cause RSEQ abort. Restoring the instruction pointer within the critical section is problematic because rseq_cs may get cleared before the control is passed to the migrated application code leading to RSEQ invariants not being preserved. C/R code will use RSEQ ABI address to find the abort handler to which the instruction pointer needs to be set. To achieve above goals expose the RSEQ ABI address and the signature value with the new ptrace request PTRACE_GET_RSEQ_CONFIGURATION. This new ptrace request can also be used by debuggers so they are aware of stops within restartable sequences in progress.
Showing the changes to include/uapi (1 of 2 files). Show all
Unified · Split
| @@ -102,6 +102,16 @@ struct ptrace_syscall_info { · 101 unmodified lines | ||
| 102 | 102 | }; |
| 103 | 103 | }; |
| 104 | 104 | |
| 105 | +#define PTRACE_GET_RSEQ_CONFIGURATION 0x420f | |
| 106 | + | |
| 107 | +struct ptrace_rseq_configuration { | |
| 108 | + __u64 rseq_abi_pointer; | |
| 109 | + __u32 rseq_abi_size; | |
| 110 | + __u32 signature; | |
| 111 | + __u32 flags; | |
| 112 | + __u32 pad; | |
| 113 | +}; | |
| 114 | + | |
| 105 | 115 | /* |
| 106 | 116 | * These values are stored in task->ptrace_message |
| 107 | 117 | * by tracehook_report_syscall_* to describe the current syscall-stop. |