diff options
| author | Michael Jeanson <mjeanson@efficios.com> | 2024-11-20 14:15:42 -0500 |
|---|---|---|
| committer | Michael Jeanson <mjeanson@efficios.com> | 2024-12-06 16:05:27 +0000 |
| commit | b2ab6ce0f5a9fa4631a8cc55bdf652deaa5dc47c (patch) | |
| tree | 49f39f5f776fab88f66f2d1bdde054b68931648f | |
| parent | 4b2b81deb431e61d6128047ffec3d5029790afa5 (diff) | |
nptl: initialize cpu_id_start prior to rseq registration
When adding explicit initialization of rseq fields prior to
registration, I glossed over the fact that 'cpu_id_start' is also
documented as initialized by user-space.
While current kernels don't validate the content of this field on
registration, future ones could.
Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
(cherry picked from commit d9f40387d3305d97e30a8cf8724218c42a63680a)
| -rw-r--r-- | sysdeps/unix/sysv/linux/rseq-internal.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/sysdeps/unix/sysv/linux/rseq-internal.h b/sysdeps/unix/sysv/linux/rseq-internal.h index 8fd26f335e..0ad79174bd 100644 --- a/sysdeps/unix/sysv/linux/rseq-internal.h +++ b/sysdeps/unix/sysv/linux/rseq-internal.h @@ -56,6 +56,7 @@ rseq_register_current_thread (struct pthread *self, bool do_rseq) registration, there is no guarantee that struct pthread is cleared on all architectures. */ THREAD_SETMEM (self, rseq_area.cpu_id, RSEQ_CPU_ID_UNINITIALIZED); + THREAD_SETMEM (self, rseq_area.cpu_id_start, 0); THREAD_SETMEM (self, rseq_area.rseq_cs, 0); THREAD_SETMEM (self, rseq_area.flags, 0); |