From: Peter Collingbourne <pcc@google.com>
To: Andrey Konovalov <andreyknvl@gmail.com>,
Alexander Potapenko <glider@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Collingbourne <pcc@google.com>,
Evgenii Stepanov <eugenis@google.com>,
linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] arm64: improve efficiency of setting tags for user pages
Date: Tue, 11 May 2021 16:54:23 -0700 [thread overview]
Message-ID: <cover.1620777150.git.pcc@google.com> (raw)
Currently we can end up touching PROT_MTE user pages twice on fault
and once on unmap. On fault, with KASAN disabled we first clear data
and then set tags to 0, and with KASAN enabled we simultaneously
clear data and set tags to the KASAN random tag, and then set tags
again to 0. On unmap, we poison the page by setting tags, but this
is less likely to find a bug than poisoning kernel pages.
This patch series fixes these inefficiencies by only touching the pages
once on fault using the DC GZVA instruction to clear both data and
tags, and providing the option to avoid poisoning user pages on free.
Peter Collingbourne (3):
kasan: use separate (un)poison implementation for integrated init
arm64: mte: handle tags zeroing at page allocation time
kasan: allow freed user page poisoning to be disabled with HW tags
arch/arm64/include/asm/mte.h | 4 ++
arch/arm64/include/asm/page.h | 9 ++++-
arch/arm64/lib/mte.S | 20 ++++++++++
arch/arm64/mm/fault.c | 25 +++++++++++++
arch/arm64/mm/proc.S | 10 +++--
include/linux/gfp.h | 18 +++++++--
include/linux/highmem.h | 8 ++++
include/linux/kasan.h | 66 ++++++++++++++++++++-------------
include/linux/page-flags.h | 9 +++++
include/trace/events/mmflags.h | 9 ++++-
mm/kasan/common.c | 4 +-
mm/kasan/hw_tags.c | 31 ++++++++++++++++
mm/mempool.c | 6 ++-
mm/page_alloc.c | 67 ++++++++++++++++++++--------------
14 files changed, 221 insertions(+), 65 deletions(-)
--
2.31.1.607.g51e8a6a459-goog
next reply other threads:[~2021-05-11 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 23:54 Peter Collingbourne [this message]
2021-05-11 23:54 ` [PATCH v2 1/3] kasan: use separate (un)poison implementation for integrated init Peter Collingbourne
2021-05-12 12:10 ` Catalin Marinas
2021-05-12 20:08 ` Peter Collingbourne
2021-05-11 23:54 ` [PATCH v2 2/3] arm64: mte: handle tags zeroing at page allocation time Peter Collingbourne
2021-05-12 12:12 ` Catalin Marinas
2021-05-11 23:54 ` [PATCH v2 3/3] kasan: allow freed user page poisoning to be disabled with HW tags Peter Collingbourne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1620777150.git.pcc@google.com \
--to=pcc@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=vincenzo.frascino@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).