summaryrefslogtreecommitdiffstats
path: root/mm/gup.c
diff options
context:
space:
mode:
authorLinus Torvalds2018-05-17 01:45:23 +0200
committerLinus Torvalds2018-05-17 01:45:23 +0200
commite6506eb241871d68647c53cb6d0a16299550ae97 (patch)
tree69e591c6cec5a83e9793eaa717f18089bcb80c16 /mm/gup.c
parentMerge tag 'trace-v4.17-rc5-vsprintf' of git://git.kernel.org/pub/scm/linux/ke... (diff)
parenttracing/x86/xen: Remove zero data size trace events trace_xen_mmu_flush_tlb{_... (diff)
downloadkernel-qcow2-linux-e6506eb241871d68647c53cb6d0a16299550ae97.tar.gz
kernel-qcow2-linux-e6506eb241871d68647c53cb6d0a16299550ae97.tar.xz
kernel-qcow2-linux-e6506eb241871d68647c53cb6d0a16299550ae97.zip
Merge tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fix from Steven Rostedt: "Some of the ftrace internal events use a zero for a data size of a field event. This is increasingly important for the histogram trigger work that is being extended. While auditing trace events, I found that a couple of the xen events were used as just marking that a function was called, by creating a static array of size zero. This can play havoc with the tracing features if these events are used, because a zero size of a static array is denoted as a special nul terminated dynamic array (this is what the trace_marker code uses). But since the xen events have no size, they are not nul terminated, and unexpected results may occur. As trace events were never intended on being a marker to denote that a function was hit or not, especially since function tracing and kprobes can trivially do the same, the best course of action is to simply remove these events" * tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: tracing/x86/xen: Remove zero data size trace events trace_xen_mmu_flush_tlb{_all}
Diffstat (limited to 'mm/gup.c')
0 files changed, 0 insertions, 0 deletions