From: Dmitry Vyukov <dvyukov@google.com>
To: Chanho Min <chanho.min@lge.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
elver@google.com, kasan-dev@googlegroups.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
gunho.lee@lge.com
Subject: Re: [PATCH] kasan: fix mention for KASAN_HW_TAGS
Date: Mon, 19 Jun 2023 12:14:49 +0200 [thread overview]
Message-ID: <CACT4Y+Zn49-6R00buq-y_H0qs=4gBh6PBsJDFBptL8=h6GPQYA@mail.gmail.com> (raw)
In-Reply-To: <20230619101224.22978-1-chanho.min@lge.com>
On Mon, 19 Jun 2023 at 12:12, Chanho Min <chanho.min@lge.com> wrote:
>
> This patch removes description of the KASAN_HW_TAGS's memory consumption.
> KASAN_HW_TAGS does not set 1/32nd shadow memory.
The hardware still allocates/uses shadow in MTE.
Though, it may be 1/16-th, not sure.
> Signed-off-by: Chanho Min <chanho.min@lge.com>
> ---
> lib/Kconfig.kasan | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan
> index fdca89c05745..5be1740234b9 100644
> --- a/lib/Kconfig.kasan
> +++ b/lib/Kconfig.kasan
> @@ -124,8 +124,6 @@ config KASAN_HW_TAGS
> Supported only on arm64 CPUs starting from ARMv8.5 and relies on
> Memory Tagging Extension and Top Byte Ignore.
>
> - Consumes about 1/32nd of available memory.
> -
> May potentially introduce problems related to pointer casting and
> comparison, as it embeds a tag into the top byte of each pointer.
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-06-19 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 10:12 Chanho Min
2023-06-19 10:14 ` Dmitry Vyukov [this message]
2023-06-19 11:36 ` Marco Elver
2023-06-20 16:32 ` Andrey Konovalov
2023-06-23 7:58 ` [PATCH v2] " Chanho Min
2023-06-23 12:40 ` Andrey Konovalov
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='CACT4Y+Zn49-6R00buq-y_H0qs=4gBh6PBsJDFBptL8=h6GPQYA@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=andreyknvl@gmail.com \
--cc=chanho.min@lge.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gunho.lee@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--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