summaryrefslogtreecommitdiff
path: root/kernel/irq_work.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2014-05-08 14:17:13 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2014-05-08 14:17:13 -0700
commitf322e262386d155c4b543f51c9939dca525a2948 (patch)
tree9b4830ee578bc9058496ec4094392414cd5112f3 /kernel/irq_work.c
parentd86561b4c7473ad43e365afdba2142b75907c9d2 (diff)
parent8058bd0faad860e75547cc5cb5d4ade016247a79 (diff)
Merge tag 'trace-fixes-v3.15-rc4-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fixes from Steven Rostedt: "This contains two fixes. The first is a long standing bug that causes bogus data to show up in the refcnt field of the module_refcnt tracepoint. It was introduced by a merge conflict resolution back in 2.6.35-rc days. The result should be 'refcnt = incs - decs', but instead it did 'refcnt = incs + decs'. The second fix is to a bug that was introduced in this merge window that allowed for a tracepoint funcs pointer to be used after it was freed. Moving the location of where the probes are released solved the problem" * tag 'trace-fixes-v3.15-rc4-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: tracepoint: Fix use of tracepoint funcs after rcu free trace: module: Maintain a valid user count
Diffstat (limited to 'kernel/irq_work.c')
0 files changed, 0 insertions, 0 deletions