diff options
author | Oleg Nesterov <oleg@redhat.com> | 2014-04-13 20:59:38 +0200 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2014-06-21 00:15:26 -0400 |
commit | ea73c79e33c45e1fa0071e216f06fd5682314490 (patch) | |
tree | d1159b8993d462f28d8862e8839f3572d8f66e9a /samples | |
parent | 8063e41d2ffc0b0ce974ea802158be35902072f3 (diff) | |
download | linux-stable-ea73c79e33c45e1fa0071e216f06fd5682314490.tar.gz linux-stable-ea73c79e33c45e1fa0071e216f06fd5682314490.tar.bz2 linux-stable-ea73c79e33c45e1fa0071e216f06fd5682314490.zip |
tracing: syscall_regfunc() should not skip kernel threads
syscall_regfunc() ignores the kernel threads because "it has no effect",
see cc3b13c1 "Don't trace kernel thread syscalls" which added this check.
However, this means that a user-space task spawned by call_usermodehelper()
will run without TIF_SYSCALL_TRACEPOINT if sys_tracepoint_refcount != 0.
Remove this check. The unnecessary report from ret_from_fork path mentioned
by cc3b13c1 is no longer possible, see See commit fb45550d76bb5 "make sure
that kernel_thread() callbacks call do_exit() themselves".
A kernel_thread() callback can only return and take the int_ret_from_sys_call
path after do_execve() succeeds, otherwise the kernel will crash. But in this
case it is no longer a kernel thread and thus is needs TIF_SYSCALL_TRACEPOINT.
Link: http://lkml.kernel.org/p/20140413185938.GD20668@redhat.com
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions