fs/proc: Expose RSEQ configuration
Subsystems (5)
PATCH v4 1/1 fs/proc: Expose RSEQ configuration
For userspace checkpoint and restore (C/R) some 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.
To achieve above goals expose the RSEQ ABI address and the signature value with the new procfs file "/proc/<pid>/rseq".
---
v4:
- added documentation and extended comment before task_lock()
v3:
- added locking so that the proc file always shows consistent pair of RSEQ ABI address and the signature
- changed string formatting to use %px for the RSEQ ABI address
v2:
- fixed string formatting for 32-bit architectures
v1:
- https://lkml.kernel.org/r/[email protected]
--- Documentation/filesystems/proc.rst | 16 ++++++++++++++++ fs/exec.c | 2 ++ fs/proc/base.c | 22 ++++++++++++++++++++++ include/linux/sched/task.h | 3 ++- kernel/rseq.c | 4 ++++ 5 files changed, 46 insertions(+), 1 deletion(-)
Documentation/filesystems/proc.rst +16 -0
@@ -47,6 +47,7 @@ fixes/update part 1.1 Stefani Seibold <[email protected]> June 9 2009 3.10 /proc/<pid>/timerslack_ns - Task timerslack value 3.11 /proc/<pid>/patch_state - Livepatch patch operation state 3.12 /proc/<pid>/arch_status - Task architecture specific information + 3.13 /proc/<pid>/rseq - RSEQ configuration state 4 Configuring procfs 4.1 Mount options
@@ -2131,6 +2132,21 @@ AVX512_elapsed_ms the task is unlikely an AVX512 user, but depends on the workload and the scheduling scenario, it also could be a false negative mentioned above. +3.13 /proc/<pid>/rseq - RSEQ configuration state +--------------------------------------------------- +This file provides RSEQ configuration of a thread. Available fields correspond +to the rseq() syscall parameters and are: + + - RSEQ ABI structure address shared between the kernel and user-space + - signature value expected before the abort handler code + +Both values are in hexadecimal format, for example:: + + # cat /proc/12345/rseq + 0000abcdef12340 aabb0011 + +This file is only present if CONFIG_RSEQ is enabled. + Chapter 4: Configuring procfs =============================
fs/exec.c +2 -0
@@ -1830,7 +1830,9 @@ static int bprm_execve(struct linux_binprm *bprm,/* execve succeeded */ current->fs->in_exec =0 ; current->in_execve =0 ; +task_lock (current);rseq_execve (current); +task_unlock (current);acct_update_integrals (current);task_numa_free (current, false);return retval;
fs/proc/base.c +22 -0
@@ -662,6 +662,22 @@ static int proc_pid_syscall(struct seq_file *m, struct pid_namespace *ns, return 0; } + +#ifdef CONFIG_RSEQ +static int proc_pid_rseq (struct seq_file *m,struct pid_namespace *ns, +struct pid *pid,struct task_struct *task) +{ +int res =lock_trace (task); + +if (res) +return res; +task_lock (task); +seq_printf (m,"%px %08x\n" , task->rseq, task->rseq_sig); +task_unlock (task); +unlock_trace (task); +return 0 ; +} +#endif /* CONFIG_RSEQ */ #endif /* CONFIG_HAVE_ARCH_TRACEHOOK */ /************************************************************************/
@@ -3182,6 +3198,9 @@ static const struct pid_entry tgid_base_stuff[] = { REG("comm", S_IRUGO|S_IWUSR, proc_pid_set_comm_operations),#ifdef CONFIG_HAVE_ARCH_TRACEHOOK ONE("syscall", S_IRUSR, proc_pid_syscall), +#ifdef CONFIG_RSEQ + ONE("rseq", S_IRUSR, proc_pid_rseq), +#endif #endif REG ("cmdline" ,S_IRUGO , proc_pid_cmdline_ops), ONE("stat", S_IRUGO, proc_tgid_stat),
@@ -3522,6 +3541,9 @@ static const struct pid_entry tid_base_stuff[] = { &proc_pid_set_comm_operations, {}),#ifdef CONFIG_HAVE_ARCH_TRACEHOOK ONE("syscall", S_IRUSR, proc_pid_syscall), +#ifdef CONFIG_RSEQ + ONE("rseq", S_IRUSR, proc_pid_rseq), +#endif #endif REG ("cmdline" ,S_IRUGO , proc_pid_cmdline_ops), ONE("stat", S_IRUGO, proc_tid_stat),
include/linux/sched/task.h +2 -1
@@ -155,7 +155,8 @@ static inline struct vm_struct *task_stack_vm_area(const struct task_struct *t)* Protects ->fs, ->files, ->mm, ->group_info, ->comm, keyring * subscriptions and synchronises with wait4(). Also used in procfs. Also * pins the final release of task.io_context. Also protects ->cpuset and -* ->cgroup.subsys[]. And ->vfork_done. +* ->cgroup.subsys[]. And ->vfork_done. And ->rseq and ->rseq_sig to +* synchronize changes with procfs reader. * * Nests both inside and outside of read_lock(&tasklist_lock). * It must not be nested with write_lock_irq(&tasklist_lock),
kernel/rseq.c +4 -0
@@ -322,8 +322,10 @@ SYSCALL_DEFINE4(rseq, struct rseq __user *, rseq, u32, rseq_len, ret =rseq_reset_rseq_cpu_id (current);if (ret)return ret; +task_lock (current); current->rseq =NULL ; current->rseq_sig =0 ; +task_unlock (current);return 0 ; }
@@ -353,8 +355,10 @@ SYSCALL_DEFINE4(rseq, struct rseq __user *, rseq, u32, rseq_len,return -EINVAL ;if (!access_ok (rseq, rseq_len))return -EFAULT ; +task_lock (current); current->rseq = rseq; current->rseq_sig = sig; +task_unlock (current);/* * If rseq was previously inactive, and has just been * registered, ensure the cpu_id_start and cpu_id fields
Signature · 1 line
2.30.0.478.g8a0d178c01-goog
Quoted 2 lines · Piotr Figiel
For userspace checkpoint and restore (C/R) some way of getting process state containing RSEQ configuration is needed.
[...]
Quoted 2 lines
To achieve above goals expose the RSEQ ABI address and the signature value with the new procfs file "/proc/<pid>/rseq".
For the record: this idea was dropped in favor of ptrace approach, as discussed over separate mail thread with Mathieu Desnoyers and Peter Zijlstra. The equivalent ptrace patch in its current version is here:
https://lore.kernel.org/lkml/[email protected]/
Best regards,
Piotr.