summaryrefslogtreecommitdiffstats
path: root/kernel/fork.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-01-07 12:42:22 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2016-01-07 12:42:22 -0800
commit2626820d838f9e98f323bf47b4fb7722d1c52e53 (patch)
tree24e6a71ca7fa285e0f6374cf977ebd98b6f935bd /kernel/fork.c
parentb06f3a168cdcd80026276898fd1fee443ef25743 (diff)
parent049fb9bd416077b3622d317a45796be4f2431df3 (diff)
downloadlinux-2626820d838f9e98f323bf47b4fb7722d1c52e53.tar.bz2
Merge tag 'trace-v4.4-rc4-4' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull ftrace fix from Steven Rostedt: "PeiyangX Qiu reported that if a module fails to load between calling ftrace_module_init() and do_init_module() that the allocations made in ftrace_module_init() will not be freed, resulting in a memory leak. The solution is to call ftrace_release_mod() on the failing module in the fail path befor do_init_module() is called. This will remove any allocations made for that module, and nothing if ftrace_module_init() wasn't called yet for that module. Note, once do_init_module() is called, the MODULE_GOING notifiers are called for the failed module, which calls into the ftrace code to do the proper clean up (basically calling ftrace_release_mod())" * tag 'trace-v4.4-rc4-4' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: ftrace/module: Call clean up function when module init fails early
Diffstat (limited to 'kernel/fork.c')
0 files changed, 0 insertions, 0 deletions