diff options
author | Gabriel Krisman Bertazi <krisman@collabora.com> | 2021-02-03 21:00:48 +0300 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2021-02-06 02:21:42 +0300 |
commit | 6342adcaa683c2b705c24ed201dc11b35854c88d (patch) | |
tree | d75d12186c1d9e79168bdd0b84740d7701bee408 /tools/include/trace/events | |
parent | 1048ba83fb1c00cd24172e23e8263972f6b5d9ac (diff) | |
download | linux-6342adcaa683c2b705c24ed201dc11b35854c88d.tar.xz |
entry: Ensure trap after single-step on system call return
Commit 299155244770 ("entry: Drop usage of TIF flags in the generic syscall
code") introduced a bug on architectures using the generic syscall entry
code, in which processes stopped by PTRACE_SYSCALL do not trap on syscall
return after receiving a TIF_SINGLESTEP.
The reason is that the meaning of TIF_SINGLESTEP flag is overloaded to
cause the trap after a system call is executed, but since the above commit,
the syscall call handler only checks for the SYSCALL_WORK flags on the exit
work.
Split the meaning of TIF_SINGLESTEP such that it only means single-step
mode, and create a new type of SYSCALL_WORK to request a trap immediately
after a syscall in single-step mode. In the current implementation, the
SYSCALL_WORK flag shadows the TIF_SINGLESTEP flag for simplicity.
Update x86 to flip this bit when a tracer enables single stepping.
Fixes: 299155244770 ("entry: Drop usage of TIF flags in the generic syscall code")
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Kyle Huey <me@kylehuey.com>
Link: https://lore.kernel.org/r/87h7mtc9pr.fsf_-_@collabora.com
Diffstat (limited to 'tools/include/trace/events')
0 files changed, 0 insertions, 0 deletions