From: Catalin Marinas <catalin.marinas@arm.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Will Deacon <will.deacon@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Evgenii Stepanov <eugenis@google.com>,
Branislav Rankov <Branislav.Rankov@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 28/43] arm64: mte: Reset the page tag in page->flags
Date: Thu, 5 Nov 2020 15:59:00 +0000 [thread overview]
Message-ID: <20201105155859.GA30030@gaia> (raw)
In-Reply-To: <fc9e96c022a147120b67056525362abb43b2a0ce.1604531793.git.andreyknvl@google.com>
On Thu, Nov 05, 2020 at 12:18:43AM +0100, Andrey Konovalov wrote:
> diff --git a/arch/arm64/kernel/mte.c b/arch/arm64/kernel/mte.c
> index 8f99c65837fd..06ba6c923ab7 100644
> --- a/arch/arm64/kernel/mte.c
> +++ b/arch/arm64/kernel/mte.c
> @@ -34,6 +34,7 @@ static void mte_sync_page_tags(struct page *page, pte_t *ptep, bool check_swap)
> return;
> }
>
> + page_kasan_tag_reset(page);
> mte_clear_page_tags(page_address(page));
I think we need an smp_wmb() between setting the flags and clearing the
actual tags. If another threads reads page->flags and builds a tagged
address out of it (see page_to_virt) there's an address dependency to
the actual memory access. However, on the current thread, we don't
guarantee that the new page->flags are visible before the tags were
updated.
> }
>
> diff --git a/arch/arm64/mm/copypage.c b/arch/arm64/mm/copypage.c
> index 70a71f38b6a9..348f4627da08 100644
> --- a/arch/arm64/mm/copypage.c
> +++ b/arch/arm64/mm/copypage.c
> @@ -22,6 +22,7 @@ void copy_highpage(struct page *to, struct page *from)
> copy_page(kto, kfrom);
>
> if (system_supports_mte() && test_bit(PG_mte_tagged, &from->flags)) {
> + page_kasan_tag_reset(to);
> set_bit(PG_mte_tagged, &to->flags);
> mte_copy_page_tags(kto, kfrom);
Nitpick: move page_kasan_tag_reset() just above mte_copy_page_tags() for
consistency with the other places where PG_mte_tagged is set before or
after the actual tag setting.
> }
> diff --git a/arch/arm64/mm/mteswap.c b/arch/arm64/mm/mteswap.c
> index c52c1847079c..0e7eccbe598a 100644
> --- a/arch/arm64/mm/mteswap.c
> +++ b/arch/arm64/mm/mteswap.c
> @@ -53,6 +53,7 @@ bool mte_restore_tags(swp_entry_t entry, struct page *page)
> if (!tags)
> return false;
>
> + page_kasan_tag_reset(page);
> mte_restore_page_tags(page_address(page), tags);
There is another mte_restore_page_tags() caller in hibernate.c. That one
doesn't need page_kasan_tag_reset() since the page->flags would have
been already restored but please add a comment in that file why its not
needed.
--
Catalin
next parent reply other threads:[~2020-11-05 16:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1604531793.git.andreyknvl@google.com>
[not found] ` <fc9e96c022a147120b67056525362abb43b2a0ce.1604531793.git.andreyknvl@google.com>
2020-11-05 15:59 ` Catalin Marinas [this message]
2020-11-06 11:46 ` [PATCH v8 28/43] arm64: mte: Reset the page tag in page->flags Vincenzo Frascino
[not found] ` <eb6ecc9ca7d4dfa653fce0012bd1651e157638e8.1604531793.git.andreyknvl@google.com>
2020-11-05 15:59 ` [PATCH v8 17/43] kasan, arm64: move initialization message Catalin Marinas
[not found] ` <f931d074bccbdf96ad91a34392d009fece081f59.1604531793.git.andreyknvl@google.com>
2020-11-05 16:00 ` [PATCH v8 18/43] kasan, arm64: rename kasan_init_tags and mark as __init Catalin Marinas
[not found] ` <a540ab7b9e3b908e0f4cd94c963a0cc6bb4e7d3f.1604531793.git.andreyknvl@google.com>
2020-11-05 16:57 ` [PATCH v8 29/43] arm64: mte: Add in-kernel tag fault handler Catalin Marinas
[not found] ` <5e3c76cac4b161fe39e3fc8ace614400bc2fb5b1.1604531793.git.andreyknvl@google.com>
2020-11-05 11:16 ` [PATCH v8 30/43] arm64: kasan: Allow enabling in-kernel MTE Vincenzo Frascino
2020-11-05 11:35 ` Andrey Konovalov
2020-11-05 11:42 ` Vincenzo Frascino
2020-11-05 12:14 ` Andrey Konovalov
2020-11-05 14:17 ` Vincenzo Frascino
2020-11-05 17:27 ` Andrey Konovalov
2020-11-05 17:25 ` Catalin Marinas
2020-11-05 17:29 ` Andrey Konovalov
2020-11-05 17:39 ` Catalin Marinas
2020-11-05 18:09 ` Andrey Konovalov
2020-11-06 11:11 ` Vincenzo Frascino
[not found] ` <5d9ece04df8e9d60e347a2f6f96b8c52316bfe66.1604531793.git.andreyknvl@google.com>
2020-11-05 17:30 ` [PATCH v8 32/43] arm64: mte: Switch GCR_EL1 in kernel entry and exit Catalin Marinas
2020-11-05 17:33 ` Andrey Konovalov
2020-11-05 17:42 ` Catalin Marinas
[not found] ` <12faf1f7dc2d3f672f856e141dd9542e8a7cc7c1.1604531793.git.andreyknvl@google.com>
2020-11-05 17:32 ` [PATCH v8 37/43] kasan, arm64: expand CONFIG_KASAN checks Catalin Marinas
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=20201105155859.GA30030@gaia \
--to=catalin.marinas@arm.com \
--cc=Branislav.Rankov@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@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).