From: Andrey Konovalov <andreyknvl@gmail.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
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>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kasan: Add abbreviation KASAN to init log
Date: Mon, 13 Apr 2026 17:05:50 +0200 [thread overview]
Message-ID: <CA+fCnZcsPehxMCP0v99Q4nsrTiEq79YKou-O8U_iRK-wBmTf1w@mail.gmail.com> (raw)
In-Reply-To: <ce76f184-e463-4bfa-afab-0a71f05eb587@molgen.mpg.de>
On Mon, Apr 13, 2026 at 3:54 PM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> > 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?
I think we can add the generalization just in case more pr_info calls
get added in the future. And also to keep the code similar to the
other modes.
>
> > 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.
Makes sense.
Thanks!
prev parent reply other threads:[~2026-04-13 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 9:40 Paul Menzel
2026-04-13 12:29 ` Alexander Potapenko
2026-04-13 12:37 ` Andrey Konovalov
2026-04-13 13:54 ` Paul Menzel
2026-04-13 15:05 ` 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+fCnZcsPehxMCP0v99Q4nsrTiEq79YKou-O8U_iRK-wBmTf1w@mail.gmail.com \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--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=pmenzel@molgen.mpg.de \
--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