From: Catalin Marinas <catalin.marinas@arm.com>
To: andreyknvl@gmail.com, Peter Collingbourne <pcc@google.com>
Cc: Will Deacon <will@kernel.org>,
Qun-wei Lin <Qun-wei.Lin@mediatek.com>,
Guangye Yang <guangye.yang@mediatek.com>,
linux-mm@kvack.org, Chinwen Chang <chinwen.chang@mediatek.com>,
kasan-dev@googlegroups.com, ryabinin.a.a@gmail.com,
linux-arm-kernel@lists.infradead.org, vincenzo.frascino@arm.com,
eugenis@google.com, Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] arm64: Reset KASAN tag in copy_highpage with HW tags only
Date: Wed, 22 Feb 2023 16:46:56 +0000 [thread overview]
Message-ID: <167708438950.477413.8786796815107449095.b4-ty@arm.com> (raw)
In-Reply-To: <20230215050911.1433132-1-pcc@google.com>
On Tue, 14 Feb 2023 21:09:11 -0800, Peter Collingbourne wrote:
> During page migration, the copy_highpage function is used to copy the
> page data to the target page. If the source page is a userspace page
> with MTE tags, the KASAN tag of the target page must have the match-all
> tag in order to avoid tag check faults during subsequent accesses to the
> page by the kernel. However, the target page may have been allocated in
> a number of ways, some of which will use the KASAN allocator and will
> therefore end up setting the KASAN tag to a non-match-all tag. Therefore,
> update the target page's KASAN tag to match the source page.
>
> [...]
Applied to arm64 (for-next/core), thanks!
[1/1] arm64: Reset KASAN tag in copy_highpage with HW tags only
https://git.kernel.org/arm64/c/e74a68468062
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: andreyknvl@gmail.com, Peter Collingbourne <pcc@google.com>
Cc: Will Deacon <will@kernel.org>,
Qun-wei Lin <Qun-wei.Lin@mediatek.com>,
Guangye Yang <guangye.yang@mediatek.com>,
linux-mm@kvack.org, Chinwen Chang <chinwen.chang@mediatek.com>,
kasan-dev@googlegroups.com, ryabinin.a.a@gmail.com,
linux-arm-kernel@lists.infradead.org, vincenzo.frascino@arm.com,
eugenis@google.com, Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] arm64: Reset KASAN tag in copy_highpage with HW tags only
Date: Wed, 22 Feb 2023 16:46:56 +0000 [thread overview]
Message-ID: <167708438950.477413.8786796815107449095.b4-ty@arm.com> (raw)
In-Reply-To: <20230215050911.1433132-1-pcc@google.com>
On Tue, 14 Feb 2023 21:09:11 -0800, Peter Collingbourne wrote:
> During page migration, the copy_highpage function is used to copy the
> page data to the target page. If the source page is a userspace page
> with MTE tags, the KASAN tag of the target page must have the match-all
> tag in order to avoid tag check faults during subsequent accesses to the
> page by the kernel. However, the target page may have been allocated in
> a number of ways, some of which will use the KASAN allocator and will
> therefore end up setting the KASAN tag to a non-match-all tag. Therefore,
> update the target page's KASAN tag to match the source page.
>
> [...]
Applied to arm64 (for-next/core), thanks!
[1/1] arm64: Reset KASAN tag in copy_highpage with HW tags only
https://git.kernel.org/arm64/c/e74a68468062
--
Catalin
_______________________________________________
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:[~2023-02-22 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 5:09 [PATCH v2] arm64: Reset KASAN tag in copy_highpage with HW tags only Peter Collingbourne
2023-02-15 5:09 ` Peter Collingbourne
2023-02-17 10:05 ` Andrey Konovalov
2023-02-17 10:05 ` Andrey Konovalov
2023-02-22 16:46 ` Catalin Marinas [this message]
2023-02-22 16:46 ` 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=167708438950.477413.8786796815107449095.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=Kuan-Ying.Lee@mediatek.com \
--cc=Qun-wei.Lin@mediatek.com \
--cc=andreyknvl@gmail.com \
--cc=chinwen.chang@mediatek.com \
--cc=eugenis@google.com \
--cc=guangye.yang@mediatek.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=stable@vger.kernel.org \
--cc=vincenzo.frascino@arm.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: link
Be 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.