diff options
author | 2020-12-07 11:20:26 -0800 | |
---|---|---|
committer | 2020-12-07 11:20:26 -0800 | |
commit | cd796ed3345030aa1bb332fe5c793b3dddaf56e7 (patch) | |
tree | ea486af6d61fec8e41c50a59eb40c27963f42dd9 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | Linux 5.10-rc7 (diff) | |
parent | tracing: Fix userstacktrace option for instances (diff) | |
download | wireguard-linux-cd796ed3345030aa1bb332fe5c793b3dddaf56e7.tar.xz wireguard-linux-cd796ed3345030aa1bb332fe5c793b3dddaf56e7.zip |
Merge tag 'trace-v5.10-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fix from Steven Rostedt:
"Fix userstacktrace option for instances
While writing an application that requires user stack trace option to
work in instances, I found that the instance option has a bug that
makes it a nop. The check for performing the user stack trace in an
instance, checks the top level options (not the instance options) to
determine if a user stack trace should be performed or not.
This is not only incorrect, but also confusing for users. It confused
me for a bit!"
* tag 'trace-v5.10-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
tracing: Fix userstacktrace option for instances
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions