From: Vincenzo Frascino <vincenzo.frascino@arm.com> To: Catalin Marinas <catalin.marinas@arm.com>, Andrey Ryabinin <ryabinin.a.a@gmail.com>, Andrey Konovalov <andreyknvl@gmail.com> Cc: Will Deacon <will@kernel.org>, Peter Collingbourne <pcc@google.com>, kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 1/4] mm: kasan: Ensure the tags are visible before the tag in page->flags Date: Thu, 16 Jun 2022 09:31:50 +0100 [thread overview] Message-ID: <8982344a-c726-934c-70fc-011b8b83bdd2@arm.com> (raw) In-Reply-To: <20220610152141.2148929-2-catalin.marinas@arm.com> On 6/10/22 16:21, Catalin Marinas wrote: > __kasan_unpoison_pages() colours the memory with a random tag and stores > it in page->flags in order to re-create the tagged pointer via > page_to_virt() later. When the tag from the page->flags is read, ensure > that the in-memory tags are already visible by re-ordering the > page_kasan_tag_set() after kasan_unpoison(). The former already has > barriers in place through try_cmpxchg(). On the reader side, the order > is ensured by the address dependency between page->flags and the memory > access. > > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com> > Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com> > Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com> > Cc: Vincenzo Frascino <vincenzo.frascino@arm.com> Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com> > --- > mm/kasan/common.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/mm/kasan/common.c b/mm/kasan/common.c > index c40c0e7b3b5f..78be2beb7453 100644 > --- a/mm/kasan/common.c > +++ b/mm/kasan/common.c > @@ -108,9 +108,10 @@ void __kasan_unpoison_pages(struct page *page, unsigned int order, bool init) > return; > > tag = kasan_random_tag(); > + kasan_unpoison(set_tag(page_address(page), tag), > + PAGE_SIZE << order, init); > for (i = 0; i < (1 << order); i++) > page_kasan_tag_set(page + i, tag); > - kasan_unpoison(page_address(page), PAGE_SIZE << order, init); > } > > void __kasan_poison_pages(struct page *page, unsigned int order, bool init) -- Regards, Vincenzo
WARNING: multiple messages have this Message-ID (diff)
From: Vincenzo Frascino <vincenzo.frascino@arm.com> To: Catalin Marinas <catalin.marinas@arm.com>, Andrey Ryabinin <ryabinin.a.a@gmail.com>, Andrey Konovalov <andreyknvl@gmail.com> Cc: Will Deacon <will@kernel.org>, Peter Collingbourne <pcc@google.com>, kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 1/4] mm: kasan: Ensure the tags are visible before the tag in page->flags Date: Thu, 16 Jun 2022 09:31:50 +0100 [thread overview] Message-ID: <8982344a-c726-934c-70fc-011b8b83bdd2@arm.com> (raw) In-Reply-To: <20220610152141.2148929-2-catalin.marinas@arm.com> On 6/10/22 16:21, Catalin Marinas wrote: > __kasan_unpoison_pages() colours the memory with a random tag and stores > it in page->flags in order to re-create the tagged pointer via > page_to_virt() later. When the tag from the page->flags is read, ensure > that the in-memory tags are already visible by re-ordering the > page_kasan_tag_set() after kasan_unpoison(). The former already has > barriers in place through try_cmpxchg(). On the reader side, the order > is ensured by the address dependency between page->flags and the memory > access. > > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com> > Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com> > Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com> > Cc: Vincenzo Frascino <vincenzo.frascino@arm.com> Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com> > --- > mm/kasan/common.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/mm/kasan/common.c b/mm/kasan/common.c > index c40c0e7b3b5f..78be2beb7453 100644 > --- a/mm/kasan/common.c > +++ b/mm/kasan/common.c > @@ -108,9 +108,10 @@ void __kasan_unpoison_pages(struct page *page, unsigned int order, bool init) > return; > > tag = kasan_random_tag(); > + kasan_unpoison(set_tag(page_address(page), tag), > + PAGE_SIZE << order, init); > for (i = 0; i < (1 << order); i++) > page_kasan_tag_set(page + i, tag); > - kasan_unpoison(page_address(page), PAGE_SIZE << order, init); > } > > void __kasan_poison_pages(struct page *page, unsigned int order, bool init) -- Regards, Vincenzo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-16 8:31 UTC|newest] Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-10 15:21 [PATCH v2 0/4] kasan: Fix ordering between MTE tag colouring and page->flags Catalin Marinas 2022-06-10 15:21 ` Catalin Marinas 2022-06-10 15:21 ` [PATCH v2 1/4] mm: kasan: Ensure the tags are visible before the tag in page->flags Catalin Marinas 2022-06-10 15:21 ` Catalin Marinas 2022-06-16 8:31 ` Vincenzo Frascino [this message] 2022-06-16 8:31 ` Vincenzo Frascino 2022-07-07 9:22 ` Will Deacon 2022-07-07 9:22 ` Will Deacon 2022-07-07 11:44 ` Catalin Marinas 2022-07-07 11:44 ` Catalin Marinas 2022-06-10 15:21 ` [PATCH v2 2/4] mm: kasan: Skip unpoisoning of user pages Catalin Marinas 2022-06-10 15:21 ` Catalin Marinas 2022-06-11 19:40 ` Andrey Konovalov 2022-06-11 19:40 ` Andrey Konovalov 2022-06-16 8:42 ` Vincenzo Frascino 2022-06-16 8:42 ` Vincenzo Frascino 2022-06-16 17:40 ` Catalin Marinas 2022-06-16 17:40 ` Catalin Marinas 2022-06-10 15:21 ` [PATCH v2 3/4] mm: kasan: Skip page unpoisoning only if __GFP_SKIP_KASAN_UNPOISON Catalin Marinas 2022-06-10 15:21 ` Catalin Marinas 2022-06-11 19:40 ` Andrey Konovalov 2022-06-11 19:40 ` Andrey Konovalov 2022-06-16 8:43 ` Vincenzo Frascino 2022-06-16 8:43 ` Vincenzo Frascino 2022-06-10 15:21 ` [PATCH v2 4/4] arm64: kasan: Revert "arm64: mte: reset the page tag in page->flags" Catalin Marinas 2022-06-10 15:21 ` Catalin Marinas 2022-06-11 19:40 ` Andrey Konovalov 2022-06-11 19:40 ` Andrey Konovalov 2022-06-16 8:44 ` Vincenzo Frascino 2022-06-16 8:44 ` Vincenzo Frascino 2022-07-07 10:33 ` [PATCH v2 0/4] kasan: Fix ordering between MTE tag colouring and page->flags Will Deacon 2022-07-07 10:33 ` Will Deacon 2022-07-08 13:31 ` Will Deacon 2022-07-08 13:31 ` Will Deacon 2023-02-02 5:25 ` Kuan-Ying Lee (李冠穎) 2023-02-02 5:25 ` Kuan-Ying Lee (李冠穎) 2023-02-02 12:59 ` Andrey Konovalov 2023-02-02 12:59 ` Andrey Konovalov 2023-02-03 3:41 ` Kuan-Ying Lee (李冠穎) 2023-02-03 3:41 ` Kuan-Ying Lee (李冠穎) 2023-02-03 17:51 ` Andrey Konovalov 2023-02-03 17:51 ` Andrey Konovalov 2023-02-08 5:41 ` Qun-wei Lin (林群崴) 2023-02-08 5:41 ` Qun-wei Lin (林群崴) 2023-02-10 6:19 ` Peter Collingbourne 2023-02-10 6:19 ` Peter Collingbourne 2023-02-10 18:28 ` Catalin Marinas 2023-02-10 18:28 ` Catalin Marinas 2023-02-10 19:03 ` Peter Collingbourne 2023-02-10 19:03 ` Peter Collingbourne 2023-02-13 18:47 ` Catalin Marinas 2023-02-13 18:47 ` Catalin Marinas 2023-02-14 1:56 ` Peter Collingbourne 2023-02-14 1:56 ` Peter Collingbourne 2023-02-13 1:56 ` Qun-wei Lin (林群崴) 2023-02-13 1:56 ` Qun-wei Lin (林群崴)
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=8982344a-c726-934c-70fc-011b8b83bdd2@arm.com \ --to=vincenzo.frascino@arm.com \ --cc=andreyknvl@gmail.com \ --cc=catalin.marinas@arm.com \ --cc=kasan-dev@googlegroups.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-mm@kvack.org \ --cc=pcc@google.com \ --cc=ryabinin.a.a@gmail.com \ --cc=will@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.