From: Andrey Konovalov <andreyknvl@gmail.com>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kasan: hw_tags: Use str_on_off() helper in kasan_init_hw_tags()
Date: Wed, 15 Jan 2025 02:45:08 +0100 [thread overview]
Message-ID: <CA+fCnZcqRnHyMfHwXFSFY_4wmhLg5jOsTsbV5oLKx=suBfNXEg@mail.gmail.com> (raw)
In-Reply-To: <20250114150935.780869-2-thorsten.blum@linux.dev>
On Tue, Jan 14, 2025 at 4:10 PM Thorsten Blum <thorsten.blum@linux.dev> wrote:
>
> Remove hard-coded strings by using the str_on_off() helper function.
>
> Suggested-by: Anshuman Khandual <anshuman.khandual@arm.com>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> mm/kasan/hw_tags.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/kasan/hw_tags.c b/mm/kasan/hw_tags.c
> index ccd66c7a4081..9a6927394b54 100644
> --- a/mm/kasan/hw_tags.c
> +++ b/mm/kasan/hw_tags.c
> @@ -16,6 +16,7 @@
> #include <linux/mm.h>
> #include <linux/static_key.h>
> #include <linux/string.h>
> +#include <linux/string_choices.h>
> #include <linux/types.h>
> #include <linux/vmalloc.h>
>
> @@ -263,8 +264,8 @@ void __init kasan_init_hw_tags(void)
>
> pr_info("KernelAddressSanitizer initialized (hw-tags, mode=%s, vmalloc=%s, stacktrace=%s)\n",
> kasan_mode_info(),
> - kasan_vmalloc_enabled() ? "on" : "off",
> - kasan_stack_collection_enabled() ? "on" : "off");
> + str_on_off(kasan_vmalloc_enabled()),
> + str_on_off(kasan_stack_collection_enabled()));
> }
>
> #ifdef CONFIG_KASAN_VMALLOC
> --
> 2.47.1
>
Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
Thanks!
prev parent reply other threads:[~2025-01-15 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 15:09 Thorsten Blum
2025-01-15 1:45 ` Andrey Konovalov [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='CA+fCnZcqRnHyMfHwXFSFY_4wmhLg5jOsTsbV5oLKx=suBfNXEg@mail.gmail.com' \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
--cc=thorsten.blum@linux.dev \
--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