diff options
| author | Catalin Marinas <catalin.marinas@arm.com> | 2022-06-10 16:21:39 +0100 |
|---|---|---|
| committer | Will Deacon <will@kernel.org> | 2022-07-07 10:48:37 +0100 |
| commit | 70c248aca9e7efa85a6664d5ab56c17c326c958f (patch) | |
| tree | 1cee0c376af4662b3f7bf8982187e3492dff1b63 /arch/arm64/mm/fault.c | |
| parent | ed0a6d1d973e9763989b44913ae1bd2a5d5d5777 (diff) | |
| download | linux-70c248aca9e7efa85a6664d5ab56c17c326c958f.tar.gz linux-70c248aca9e7efa85a6664d5ab56c17c326c958f.tar.bz2 linux-70c248aca9e7efa85a6664d5ab56c17c326c958f.zip | |
mm: kasan: Skip unpoisoning of user pages
Commit c275c5c6d50a ("kasan: disable freed user page poisoning with HW
tags") added __GFP_SKIP_KASAN_POISON to GFP_HIGHUSER_MOVABLE. A similar
argument can be made about unpoisoning, so also add
__GFP_SKIP_KASAN_UNPOISON to user pages. To ensure the user page is
still accessible via page_address() without a kasan fault, reset the
page->flags tag.
With the above changes, there is no need for the arm64
tag_clear_highpage() to reset the page->flags tag.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Andrey Konovalov <andreyknvl@gmail.com>
Cc: Peter Collingbourne <pcc@google.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
Link: https://lore.kernel.org/r/20220610152141.2148929-3-catalin.marinas@arm.com
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'arch/arm64/mm/fault.c')
| -rw-r--r-- | arch/arm64/mm/fault.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c index c5e11768e5c1..cdf3ffa0c223 100644 --- a/arch/arm64/mm/fault.c +++ b/arch/arm64/mm/fault.c @@ -927,6 +927,5 @@ struct page *alloc_zeroed_user_highpage_movable(struct vm_area_struct *vma, void tag_clear_highpage(struct page *page) { mte_zero_clear_page_tags(page_address(page)); - page_kasan_tag_reset(page); set_bit(PG_mte_tagged, &page->flags); } |