summaryrefslogtreecommitdiff
path: root/mm/percpu.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2019-03-07 09:55:56 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2019-03-07 09:55:56 -0800
commitbdfa15f1a357bb90ab715e326e86cc546b282f49 (patch)
tree9c72fafb5854c50d0d88896f0d2433d15a994729 /mm/percpu.c
parent9e1fd794cb6bf813a40849a1fc236703bdcbc1a7 (diff)
parent49ef5f45701c3dedc6aa6efee5d03756fea0f99d (diff)
Merge tag 'trace-v5.0-pre' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fix/cleanup from Steven Rostedt: "This is a "pre-pull". It's only one small fix and one small clean up. I'm testing a few small patches for my real pull request which will come at a later time. The second patch depends on your tree anyway so I included it along with the urgent fix. A small fix Pavel sent me back in august was accidentally lost due to it being placed with some other patches that failed some tests, and was rebased out of my local tree. Which was a regression that caused event filters not to handle negative numbers. The clean up is from Masami that realized that the code in kprobes that calls probe_mem_read() wrapper, which is to be used in code used by both kprobes and uprobes, was only in code for kprobes. It should not use the wrapper there, but instead call probe_kernel_read() directly" * tag 'trace-v5.0-pre' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: tracing/kprobes: Use probe_kernel_read instead of probe_mem_read tracing: Fix event filters and triggers to handle negative numbers
Diffstat (limited to 'mm/percpu.c')
0 files changed, 0 insertions, 0 deletions