summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2019-02-18 09:40:16 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2019-02-18 09:40:16 -0800
commit10f4902173130fcbb02a69566fefab35fc5f1f30 (patch)
tree51a570111e11bcdbbeb1520ee231dd749690b2ae /arch
parenta3b22b9f11d9fbc48b0291ea92259a5a810e9438 (diff)
parent9e7382153f80ba45a0bbcd540fb77d4b15f6e966 (diff)
downloadlinux-stable-10f4902173130fcbb02a69566fefab35fc5f1f30.tar.gz
linux-stable-10f4902173130fcbb02a69566fefab35fc5f1f30.tar.bz2
linux-stable-10f4902173130fcbb02a69566fefab35fc5f1f30.zip
Merge tag 'trace-v5.0-rc4-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fixes from Steven Rostedt: "Two more tracing fixes - Have kprobes not use copy_from_user() to access kernel addresses, because kprobes can legitimately poke at bad kernel memory, which will fault. Copy from user code should never fault in kernel space. Using probe_mem_read() can handle kernel address space faulting. - Put back the entries counter in the tracing output that was accidentally removed" * tag 'trace-v5.0-rc4-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: tracing: Fix number of entries in trace header kprobe: Do not use uaccess functions to access kernel memory that can fault
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions