path: root/arch
diff options
authorLinus Torvalds <torvalds@linux-foundation.org>2018-08-23 13:07:00 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2018-08-23 13:07:00 -0700
commit452938cbd8f85a39c8a93553191c505a36b1beca (patch)
treecf6e63100654569975c6ffc4d8a7e3f287b627f8 /arch
parent815f0ddb346c196018d4d8f8f55c12b83da1de3f (diff)
parent9161a864ff88e800de50494da095af19832e9583 (diff)
Merge tag 'trace-v4.19-1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fixes from Steven Rostedt: "Masami found an off by one bug in the code that keeps "notrace" functions from being traced by kprobes. During my testing, I found that there's places that we may want to add kprobes to notrace, thus we may end up changing this code before 4.19 is released. The history behind this change is that we found that adding kprobes to various notrace functions caused the kernel to crashed. We took the safe route and decided not to allow kprobes to trace any notrace function. But because notrace is added to functions that just cause weird side effects to the function tracer, but are still safe, preventing kprobes for all notrace functios may be too much of a big hammer. One such place is __schedule() is marked notrace, to keep function tracer from doing strange recursive loops when it gets traced with NEED_RESCHED set. With this change, one can not add kprobes to the scheduler. Masami also added code to use gcov on ftrace" * tag 'trace-v4.19-1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: tracing/kprobes: Fix to check notrace function with correct range tracing: Allow gcov profiling on only ftrace subsystem
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions