On 10/24, Sergey Senozhatsky wrote: > > small question, > > ptrace_notify() and forward calls are able to both indirectly and directly > call schedule(), > /* direct call from ptrace_stop()*/, > should, in this case, rcu_user_enter() be called before > tracehook_report_syscall_exit(regs, step) > and ptrace chain?
Well, I don't really understand this magic... but why? Until we return to user-mode this CPU should be in "in_user = false" state. I am not sure I understand how it is guaranteed that rcu_user_exit() was called... probably TIF_NOHZ should trigger the slow path and ensure that syscall_trace_enter()->rcu_user_exit() will be called. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
