From: David Hildenbrand <david@redhat.com>
To: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Marco Elver <elver@google.com>
Cc: chinwen.chang@mediatek.com, yee.lee@mediatek.com,
nicholas.tang@mediatek.com, kasan-dev@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3] kasan: add kasan mode messages when kasan init
Date: Fri, 22 Oct 2021 14:28:59 +0200 [thread overview]
Message-ID: <d6f6bb06-17a5-92d4-82f9-f8350d0a7b0f@redhat.com> (raw)
In-Reply-To: <20211020094850.4113-1-Kuan-Ying.Lee@mediatek.com>
On 20.10.21 11:48, Kuan-Ying Lee wrote:
> There are multiple kasan modes. It makes sense that we add some messages
> to know which kasan mode is when booting up. see [1].
s/is/is active/ ?
Looks reasonable to me
Reviewed-by: David Hildenbrand <david@redhat.com>
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=212195 [1]
> Signed-off-by: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
> ---
> v3:
> - Rebase to linux-next
> - Move kasan_mode_info() into hw_tags.c
> v2:
> - Rebase to linux-next
> - HW-tag based mode need to consider asymm mode
> - Thanks Marco's suggestion
>
> arch/arm64/mm/kasan_init.c | 2 +-
> mm/kasan/hw_tags.c | 14 +++++++++++++-
> mm/kasan/sw_tags.c | 2 +-
> 3 files changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/mm/kasan_init.c b/arch/arm64/mm/kasan_init.c
> index 5b996ca4d996..6f5a6fe8edd7 100644
> --- a/arch/arm64/mm/kasan_init.c
> +++ b/arch/arm64/mm/kasan_init.c
> @@ -309,7 +309,7 @@ void __init kasan_init(void)
> kasan_init_depth();
> #if defined(CONFIG_KASAN_GENERIC)
> /* CONFIG_KASAN_SW_TAGS also requires kasan_init_sw_tags(). */
> - pr_info("KernelAddressSanitizer initialized\n");
> + pr_info("KernelAddressSanitizer initialized (generic)\n");
> #endif
> }
>
> diff --git a/mm/kasan/hw_tags.c b/mm/kasan/hw_tags.c
> index dc892119e88f..7355cb534e4f 100644
> --- a/mm/kasan/hw_tags.c
> +++ b/mm/kasan/hw_tags.c
> @@ -106,6 +106,16 @@ static int __init early_kasan_flag_stacktrace(char *arg)
> }
> early_param("kasan.stacktrace", early_kasan_flag_stacktrace);
>
> +static inline const char *kasan_mode_info(void)
> +{
> + if (kasan_mode == KASAN_MODE_ASYNC)
> + return "async";
> + else if (kasan_mode == KASAN_MODE_ASYMM)
> + return "asymm";
> + else
> + return "sync";
> +}
> +
> /* kasan_init_hw_tags_cpu() is called for each CPU. */
> void kasan_init_hw_tags_cpu(void)
> {
> @@ -177,7 +187,9 @@ void __init kasan_init_hw_tags(void)
> break;
> }
>
> - pr_info("KernelAddressSanitizer initialized\n");
> + pr_info("KernelAddressSanitizer initialized (hw-tags, mode=%s, stacktrace=%s)\n",
> + kasan_mode_info(),
> + kasan_stack_collection_enabled() ? "on" : "off");
> }
>
> void kasan_alloc_pages(struct page *page, unsigned int order, gfp_t flags)
> diff --git a/mm/kasan/sw_tags.c b/mm/kasan/sw_tags.c
> index bd3f540feb47..77f13f391b57 100644
> --- a/mm/kasan/sw_tags.c
> +++ b/mm/kasan/sw_tags.c
> @@ -42,7 +42,7 @@ void __init kasan_init_sw_tags(void)
> for_each_possible_cpu(cpu)
> per_cpu(prng_state, cpu) = (u32)get_cycles();
>
> - pr_info("KernelAddressSanitizer initialized\n");
> + pr_info("KernelAddressSanitizer initialized (sw-tags)\n");
> }
>
> /*
>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2021-10-22 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 9:48 Kuan-Ying Lee
2021-10-20 9:58 ` Marco Elver
2021-10-20 22:29 ` Andrew Morton
2021-10-21 8:55 ` Will Deacon
2021-10-22 12:28 ` David Hildenbrand [this message]
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=d6f6bb06-17a5-92d4-82f9-f8350d0a7b0f@redhat.com \
--to=david@redhat.com \
--cc=Kuan-Ying.Lee@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=chinwen.chang@mediatek.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=nicholas.tang@mediatek.com \
--cc=ryabinin.a.a@gmail.com \
--cc=will@kernel.org \
--cc=yee.lee@mediatek.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
all inboxes | Powered by JetHome®