Mathieu Desnoyers 4842dadfc6 selftests/rseq: Fix: Fail thread registration when CONFIG_RSEQ=n ...

When linking the selftests against a libc which does not handle rseq
registration (before 2.35),  rseq thread registration silently succeed
even with CONFIG_RSEQ=n because it erroneously thinks that libc is
handling rseq registration.

This is caused by setting the rseq ownership flag only after the
rseq_available() check. It should rather be set before the
rseq_available() check.

Set the rseq_size to 0 (error value) immediately after the
rseq_available() check fails rather than in the thread registration
functions.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lore.kernel.org/r/20221122203932.231377-2-mathieu.desnoyers@efficios.com

2022-12-27 12:52:10 +01:00

..

crypto/chacha20-s390

…

cxl

…

fault-injection

…

ktest

…

kunit

…

memblock

…

nvdimm

…

radix-tree

…

scatterlist

…

selftests

selftests/rseq: Fix: Fail thread registration when CONFIG_RSEQ=n

2022-12-27 12:52:10 +01:00

vsock

…