diff options
author | Catalin Marinas <[email protected]> | 2021-02-10 18:03:16 +0000 |
---|---|---|
committer | Catalin Marinas <[email protected]> | 2021-02-12 16:08:31 +0000 |
commit | 68d54ceeec0e5fee4fb8048e6a04c193f32525ca (patch) | |
tree | b13558953da871a0dfb7ac1aebbc285fba9317c5 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 22cd5edb2d9c6d68b6ac0fc9584104d88710fa57 (diff) |
arm64: mte: Allow PTRACE_PEEKMTETAGS access to the zero page
The ptrace(PTRACE_PEEKMTETAGS) implementation checks whether the user
page has valid tags (mapped with PROT_MTE) by testing the PG_mte_tagged
page flag. If this bit is cleared, ptrace(PTRACE_PEEKMTETAGS) returns
-EIO.
A newly created (PROT_MTE) mapping points to the zero page which had its
tags zeroed during cpu_enable_mte(). If there were no prior writes to
this mapping, ptrace(PTRACE_PEEKMTETAGS) fails with -EIO since the zero
page does not have the PG_mte_tagged flag set.
Set PG_mte_tagged on the zero page when its tags are cleared during
boot. In addition, to avoid ptrace(PTRACE_PEEKMTETAGS) succeeding on
!PROT_MTE mappings pointing to the zero page, change the
__access_remote_tags() check to (vm_flags & VM_MTE) instead of
PG_mte_tagged.
Signed-off-by: Catalin Marinas <[email protected]>
Fixes: 34bfeea4a9e9 ("arm64: mte: Clear the tags when a page is mapped in user-space with PROT_MTE")
Cc: <[email protected]> # 5.10.x
Cc: Will Deacon <[email protected]>
Reported-by: Luis Machado <[email protected]>
Tested-by: Luis Machado <[email protected]>
Reviewed-by: Vincenzo Frascino <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions