diff options
author | Mathieu Desnoyers <mathieu.desnoyers@efficios.com> | 2022-06-22 22:46:16 +0300 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2022-08-01 16:21:29 +0300 |
commit | 0190e4198e47fe99d002d72588f34fd62c9ab570 (patch) | |
tree | 025ffe0425ab8aa28c0ded5bc3ca61a79019f605 /.get_maintainer.ignore | |
parent | 91caa5ae242465c3ab9fd473e50170faa7e944f4 (diff) | |
download | linux-0190e4198e47fe99d002d72588f34fd62c9ab570.tar.xz |
rseq: Deprecate RSEQ_CS_FLAG_NO_RESTART_ON_* flags
The pretty much unused RSEQ_CS_FLAG_NO_RESTART_ON_* flags introduce
complexity in rseq, and are subtly buggy [1]. Solving those issues
requires introducing additional complexity in the rseq implementation
for each supported architecture.
Considering that it complexifies the rseq ABI, I am proposing that we
deprecate those flags. [2]
So far there appears to be consensus from maintainers of user-space
projects impacted by this feature that its removal would be a welcome
simplification. [3]
The deprecation approach proposed here is to issue WARN_ON_ONCE() when
encountering those flags and kill the offending process with sigsegv.
This should allow us to quickly identify whether anyone yells at us for
removing this.
Link: https://lore.kernel.org/lkml/20220618182515.95831-1-minhquangbui99@gmail.com/ [1]
Link: https://lore.kernel.org/lkml/258546133.12151.1655739550814.JavaMail.zimbra@efficios.com/ [2]
Link: https://lore.kernel.org/lkml/87pmj1enjh.fsf@email.froward.int.ebiederm.org/ [3]
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/lkml/20220622194617.1155957-1-mathieu.desnoyers@efficios.com
Diffstat (limited to '.get_maintainer.ignore')
0 files changed, 0 insertions, 0 deletions