diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2013-01-22 10:30:49 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-01-22 10:30:49 -0800 |
commit | d26d45253b78ec0a67003eea25bd08fceaa5b78c (patch) | |
tree | ed79c581aca93bec4122943111d411ce316f5596 /usr/Kconfig | |
parent | 0944c0a03465718909ba8e800a5230528aeabafb (diff) | |
parent | c1bf08ac26e92122faab9f6c32ea8aba94612dae (diff) | |
download | op-kernel-dev-d26d45253b78ec0a67003eea25bd08fceaa5b78c.zip op-kernel-dev-d26d45253b78ec0a67003eea25bd08fceaa5b78c.tar.gz |
Merge tag 'trace-3.8-rc4-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull ftrace fix from Steven Rostedt:
"Kprobes now uses the function tracer if it can. That is, if a probe
is placed on a function mcount/nop location, and the arch supports it,
instead of adding a breakpoint, kprobes will register a function
callback as that is much more efficient.
The function tracer requires to update modules before they run, and
uses the module notifier to do so. But if something else in the
module notifiers registers a kprobe at one of these locations, before
ftrace can get to it, then the system could fail.
The function tracer must be initialized early, otherwise module
notifiers that probe will only work by chance."
* tag 'trace-3.8-rc4-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
ftrace: Be first to run code modification on modules
Diffstat (limited to 'usr/Kconfig')
0 files changed, 0 insertions, 0 deletions