summaryrefslogtreecommitdiff
path: root/arch/x86/kernel/apm_32.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-11-15 08:49:13 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2016-11-15 08:49:13 -0800
commit81bcfe5e48f9b8c42cf547f1c74c7f60c44c34c8 (patch)
tree55f6ce31dbb95c967fa19c508ccebeb02a16a1d9 /arch/x86/kernel/apm_32.c
parent80fc2f7fd8dece7bfa9b5b5dafb8705bbcefa6b4 (diff)
parent546fece4eae871f033925ccf0ff2b740725ae915 (diff)
Merge tag 'trace-v4.9-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fixes from Steven Rostedt: "Alexei discovered a race condition in modules failing to load that can cause a ftrace check to trigger and disable ftrace. This is because of the way modules are registered to ftrace. Their functions are loaded in the ftrace function tables but set to "disabled" since they are still in the process of being loaded by the module. After the module is finished, it calls back into the ftrace infrastructure to enable it. Looking deeper into the locations that access all the functions in the table, I found more locations that should ignore the disabled ones" * tag 'trace-v4.9-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: ftrace: Add more checks for FTRACE_FL_DISABLED in processing ip records ftrace: Ignore FTRACE_FL_DISABLED while walking dyn_ftrace records
Diffstat (limited to 'arch/x86/kernel/apm_32.c')
0 files changed, 0 insertions, 0 deletions