diff options
author | Kirill A. Shutemov <[email protected]> | 2023-08-09 17:46:00 +0300 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2023-08-09 08:05:23 -0700 |
commit | 22883973244b1caaa26f9c6171a41ba843c8d4bd (patch) | |
tree | 125495296da587957fde03d6f3a6dabdc85258d0 /tools/perf/scripts/python/Perf-Trace-Util/Context.c | |
parent | 77245f1c3c6495521f6a3af082696ee2f8ce3921 (diff) |
mm: Fix access_remote_vm() regression on tagged addresses
GDB uses /proc/PID/mem to access memory of the target process. GDB
doesn't untag addresses manually, but relies on kernel to do the right
thing.
mem_rw() of procfs uses access_remote_vm() to get data from the target
process. It worked fine until recent changes in __access_remote_vm()
that now checks if there's VMA at target address using raw address.
Untag the address before looking up the VMA.
Signed-off-by: Kirill A. Shutemov <[email protected]>
Reported-by: Christina Schimpe <[email protected]>
Fixes: eee9c708cc89 ("gup: avoid stack expansion warning for known-good case")
Cc: [email protected]
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/Context.c')
0 files changed, 0 insertions, 0 deletions