summaryrefslogtreecommitdiff
path: root/drivers/bluetooth
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-02-22 22:09:18 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2016-02-22 22:09:18 (GMT)
commit4de8ebeff8ddefaceeb7fc6a9b1a514fc9624509 (patch)
tree09e4096550fa34dd1e5ea6d508bb5e01b39ac612 /drivers/bluetooth
parent692b8c663cbaf892d10106fbca543b4bbc3202ad (diff)
parent6e22c8366416251a3d88ba6c92d13d595089f0ed (diff)
downloadlinux-4de8ebeff8ddefaceeb7fc6a9b1a514fc9624509.tar.xz
Merge tag 'trace-fixes-v4.5-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fixes from Steven Rostedt: "Two more small fixes. One is by Yang Shi who added a READ_ONCE_NOCHECK() to the scan of the stack made by the stack tracer. As the stack tracer scans the entire kernel stack, KASAN triggers seeing it as a "stack out of bounds" error. As the scan is looking at the contents of the stack from parent functions. The NOCHECK() tells KASAN that this is done on purpose, and is not some kind of stack overflow. The second fix is to the ftrace selftests, to retrieve the PID of executed commands from the shell with '$!' and not by parsing 'jobs'" * tag 'trace-fixes-v4.5-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: tracing, kasan: Silence Kasan warning in check_stack of stack_tracer ftracetest: Fix instance test to use proper shell command for pids
Diffstat (limited to 'drivers/bluetooth')
0 files changed, 0 insertions, 0 deletions