* [PATCH] kasan: Add abbreviation KASAN to init log
@ 2026-04-13 9:40 Paul Menzel
2026-04-13 12:29 ` Alexander Potapenko
2026-04-13 12:37 ` Andrey Konovalov
0 siblings, 2 replies; 4+ messages in thread
From: Paul Menzel @ 2026-04-13 9:40 UTC (permalink / raw)
To: Andrey Ryabinin, Alexander Potapenko, Andrey Konovalov,
Dmitry Vyukov, Vincenzo Frascino, Andrew Morton
Cc: Paul Menzel, kasan-dev, linux-mm, linux-kernel
`sudo dmesg | grep -i kasan` comes back empty, at least confusing me.
So, include the abbreviation in the log line.
Before:
KernelAddressSanitizer initialized (generic)
After:
KernelAddressSanitizer (KASAN) initialized (generic)
Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
---
mm/kasan/generic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/kasan/generic.c b/mm/kasan/generic.c
index 2b8e73f5f6a7..1fccf7cc9fce 100644
--- a/mm/kasan/generic.c
+++ b/mm/kasan/generic.c
@@ -44,7 +44,7 @@ void __init kasan_init_generic(void)
{
kasan_enable();
- pr_info("KernelAddressSanitizer initialized (generic)\n");
+ pr_info("KernelAddressSanitizer (KASAN) initialized (generic)\n");
}
/*
--
2.53.0
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] kasan: Add abbreviation KASAN to init log
2026-04-13 9:40 [PATCH] kasan: Add abbreviation KASAN to init log Paul Menzel
@ 2026-04-13 12:29 ` Alexander Potapenko
2026-04-13 12:37 ` Andrey Konovalov
1 sibling, 0 replies; 4+ messages in thread
From: Alexander Potapenko @ 2026-04-13 12:29 UTC (permalink / raw)
To: Paul Menzel
Cc: Andrey Ryabinin, Andrey Konovalov, Dmitry Vyukov,
Vincenzo Frascino, Andrew Morton, kasan-dev, linux-mm,
linux-kernel
On Mon, Apr 13, 2026 at 11:40 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> `sudo dmesg | grep -i kasan` comes back empty, at least confusing me.
Yeah, I think this bit me once or twice as well.
> So, include the abbreviation in the log line.
>
> Before:
>
> KernelAddressSanitizer initialized (generic)
>
> After:
>
> KernelAddressSanitizer (KASAN) initialized (generic)
>
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
Reviewed-by: Alexander Potapenko <glider@google.com>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] kasan: Add abbreviation KASAN to init log
2026-04-13 9:40 [PATCH] kasan: Add abbreviation KASAN to init log Paul Menzel
2026-04-13 12:29 ` Alexander Potapenko
@ 2026-04-13 12:37 ` Andrey Konovalov
2026-04-13 13:54 ` Paul Menzel
1 sibling, 1 reply; 4+ messages in thread
From: Andrey Konovalov @ 2026-04-13 12:37 UTC (permalink / raw)
To: Paul Menzel
Cc: Andrey Ryabinin, Alexander Potapenko, Dmitry Vyukov,
Vincenzo Frascino, Andrew Morton, kasan-dev, linux-mm,
linux-kernel
On Mon, Apr 13, 2026 at 11:40 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> `sudo dmesg | grep -i kasan` comes back empty, at least confusing me.
> So, include the abbreviation in the log line.
>
> Before:
>
> KernelAddressSanitizer initialized (generic)
>
> After:
>
> KernelAddressSanitizer (KASAN) initialized (generic)
>
> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
> ---
> mm/kasan/generic.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/kasan/generic.c b/mm/kasan/generic.c
> index 2b8e73f5f6a7..1fccf7cc9fce 100644
> --- a/mm/kasan/generic.c
> +++ b/mm/kasan/generic.c
> @@ -44,7 +44,7 @@ void __init kasan_init_generic(void)
> {
> kasan_enable();
>
> - pr_info("KernelAddressSanitizer initialized (generic)\n");
> + pr_info("KernelAddressSanitizer (KASAN) initialized (generic)\n");
I think a better change would be to add:
#define pr_fmt(fmt) "kasan: " fmt
to generic.c.
Similar to how this is done in sw/hw_tags.c.
And arguably, we could also drop the "KernelAddressSanitizer" part
from init messages, to make them look like:
kasan: initialized (generic)
Thank you!
> }
>
> /*
> --
> 2.53.0
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] kasan: Add abbreviation KASAN to init log
2026-04-13 12:37 ` Andrey Konovalov
@ 2026-04-13 13:54 ` Paul Menzel
0 siblings, 0 replies; 4+ messages in thread
From: Paul Menzel @ 2026-04-13 13:54 UTC (permalink / raw)
To: Andrey Konovalov
Cc: Andrey Ryabinin, Alexander Potapenko, Dmitry Vyukov,
Vincenzo Frascino, Andrew Morton, kasan-dev, linux-mm,
linux-kernel
Dear Andrey,
Am 13.04.26 um 14:37 schrieb Andrey Konovalov:
> On Mon, Apr 13, 2026 at 11:40 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>>
>> `sudo dmesg | grep -i kasan` comes back empty, at least confusing me.
>> So, include the abbreviation in the log line.
>>
>> Before:
>>
>> KernelAddressSanitizer initialized (generic)
>>
>> After:
>>
>> KernelAddressSanitizer (KASAN) initialized (generic)
>>
>> Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
>> ---
>> mm/kasan/generic.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/kasan/generic.c b/mm/kasan/generic.c
>> index 2b8e73f5f6a7..1fccf7cc9fce 100644
>> --- a/mm/kasan/generic.c
>> +++ b/mm/kasan/generic.c
>> @@ -44,7 +44,7 @@ void __init kasan_init_generic(void)
>> {
>> kasan_enable();
>>
>> - pr_info("KernelAddressSanitizer initialized (generic)\n");
>> + pr_info("KernelAddressSanitizer (KASAN) initialized (generic)\n");
>
> I think a better change would be to add:
>
> #define pr_fmt(fmt) "kasan: " fmt
>
> to generic.c.
>
> Similar to how this is done in sw/hw_tags.c.
Isn’t there only this one log line in `generic.c`, so the generalization
is not really needed?
> And arguably, we could also drop the "KernelAddressSanitizer" part
> from init messages, to make them look like:
>
> kasan: initialized (generic)
Some analysis scripts might already depend on KernelAddressSanitizer, so
I’d keep it.
Kind regards,
Paul
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-04-13 13:54 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-04-13 9:40 [PATCH] kasan: Add abbreviation KASAN to init log Paul Menzel
2026-04-13 12:29 ` Alexander Potapenko
2026-04-13 12:37 ` Andrey Konovalov
2026-04-13 13:54 ` Paul Menzel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox