From: Chanho Min <chanho.min@lge.com>
To: andreyknvl@gmail.com
Cc: chanho.min@lge.com, dvyukov@google.com, elver@google.com,
glider@google.com, gunho.lee@lge.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
ryabinin.a.a@gmail.com, vincenzo.frascino@arm.com
Subject: [PATCH v2] kasan: fix mention for KASAN_HW_TAGS
Date: Fri, 23 Jun 2023 16:58:05 +0900 [thread overview]
Message-ID: <20230623075805.1630-1-chanho.min@lge.com> (raw)
In-Reply-To: <CA+fCnZfi_o6QbfDamUjsPXjtnEwKyBn8y+T8=zxV2mEpA=DUyQ@mail.gmail.com>
This patch fixes description of the KASAN_HW_TAGS's memory consumption.
KASAN_HW_TAGS are dependent on the HW implementation and are not reserved
from system memory like shadow memory.
Suggested-by: Andrey Konovalov <andreyknvl@gmail.com>
Signed-off-by: Chanho Min <chanho.min@lge.com>
---
lib/Kconfig.kasan | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan
index fdca89c05745..f8f9e12510b7 100644
--- a/lib/Kconfig.kasan
+++ b/lib/Kconfig.kasan
@@ -124,7 +124,8 @@ 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.
+ Does not consume memory by itself but relies on the 1/32nd of
+ available memory being reserved by the firmware when MTE is enabled.
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-23 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 10:12 [PATCH] " Chanho Min
2023-06-19 10:14 ` Dmitry Vyukov
2023-06-19 11:36 ` Marco Elver
2023-06-20 16:32 ` Andrey Konovalov
2023-06-23 7:58 ` Chanho Min [this message]
2023-06-23 12:40 ` [PATCH v2] " 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=20230623075805.1630-1-chanho.min@lge.com \
--to=chanho.min@lge.com \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.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