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: Evgenii Stepanov <eugenis@google.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Marco Elver <elver@google.com>
Subject: Re: [PATCH v3 0/3] arm64: improve efficiency of setting tags for user pages
Date: Tue, 25 May 2021 12:03:53 -0700 [thread overview]
Message-ID: <CAMn1gO70R9wf_ANy3BS_OBmBzfoZjnTsX23cXNXv1wtdgMLftw@mail.gmail.com> (raw)
In-Reply-To: <cover.1620849613.git.pcc@google.com>
On Wed, May 12, 2021 at 1:09 PM Peter Collingbourne <pcc@google.com> wrote:
>
> 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
Thanks Catalin for reviewing patch 2. Could someone on the KASAN side
please take a look at patches 1 and 3?
I imagine that we'll want this series to go in via the mm tree once it's ready.
Peter
prev parent reply other threads:[~2021-05-25 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 20:09 [PATCH v3 0/3] arm64: improve efficiency of setting tags for user pages Peter Collingbourne
2021-05-12 20:09 ` [PATCH v3 1/3] kasan: use separate (un)poison implementation for integrated init Peter Collingbourne
2021-05-25 22:00 ` Andrey Konovalov
2021-05-28 1:04 ` Peter Collingbourne
2021-05-26 10:12 ` Marco Elver
2021-05-26 19:27 ` Peter Collingbourne
2021-05-26 19:54 ` Marco Elver
2021-05-12 20:09 ` [PATCH v3 2/3] arm64: mte: handle tags zeroing at page allocation time Peter Collingbourne
2021-05-25 22:00 ` Andrey Konovalov
2021-05-12 20:09 ` [PATCH v3 3/3] kasan: allow freed user page poisoning to be disabled with HW tags Peter Collingbourne
2021-05-25 22:06 ` Andrey Konovalov
2021-05-26 10:45 ` Jann Horn
2021-05-28 1:05 ` Peter Collingbourne
2021-05-25 19:03 ` Peter Collingbourne [this message]
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=CAMn1gO70R9wf_ANy3BS_OBmBzfoZjnTsX23cXNXv1wtdgMLftw@mail.gmail.com \
--to=pcc@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=elver@google.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).