summaryrefslogtreecommitdiffstats
path: root/certs/system_keyring.c
diff options
context:
space:
mode:
authorKirill A. Shutemov <kirill.shutemov@linux.intel.com>2023-08-09 16:46:00 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2023-08-09 17:05:23 +0200
commit22883973244b1caaa26f9c6171a41ba843c8d4bd (patch)
tree125495296da587957fde03d6f3a6dabdc85258d0 /certs/system_keyring.c
parentx86/CPU/AMD: Do not leak quotient data after a division by 0 (diff)
downloadlinux-22883973244b1caaa26f9c6171a41ba843c8d4bd.tar.xz
linux-22883973244b1caaa26f9c6171a41ba843c8d4bd.zip
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 <kirill.shutemov@linux.intel.com> Reported-by: Christina Schimpe <christina.schimpe@intel.com> Fixes: eee9c708cc89 ("gup: avoid stack expansion warning for known-good case") Cc: stable@vger.kernel.org Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'certs/system_keyring.c')
0 files changed, 0 insertions, 0 deletions