aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorRussell King <rmk+kernel@arm.linux.org.uk>2015-05-15 11:02:23 +0100
committerRussell King <rmk+kernel@arm.linux.org.uk>2015-05-15 11:06:35 +0100
commit1b97937246d8b97c0760d16d8992c7937bdf5e6a (patch)
treec1a283d279d553bf0b1b975ee280efe202e0087a /tools/perf/scripts/python/call-graph-from-postgresql.py
parentARM: 8356/1: mm: handle non-pmd-aligned end of RAM (diff)
downloadwireguard-linux-1b97937246d8b97c0760d16d8992c7937bdf5e6a.tar.xz
wireguard-linux-1b97937246d8b97c0760d16d8992c7937bdf5e6a.zip
ARM: fix missing syscall trace exit
Josh Stone reports: I've discovered a case where both arm and arm64 will miss a ptrace syscall-exit that they should report. If the syscall is entered without TIF_SYSCALL_TRACE set, then it goes on the fast path. It's then possible to have TIF_SYSCALL_TRACE added in the middle of the syscall, but ret_fast_syscall doesn't check this flag again. Fix this by always checking for a syscall trace in the fast exit path. Reported-by: Josh Stone <jistone@redhat.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions