[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZfVPGYkFrEaU0-AzxUDLQcwoT08XuTrXf9oifHWEbhA=g@mail.gmail.com>
Date: Thu, 4 Dec 2025 17:40:29 +0100
From: Andrey Konovalov <andreyknvl@...il.com>
To: Baoquan He <bhe@...hat.com>
Cc: linux-mm@...ck.org, ryabinin.a.a@...il.com, glider@...gle.com,
dvyukov@...gle.com, vincenzo.frascino@....com, akpm@...ux-foundation.org,
kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org, elver@...gle.com, sj@...nel.org,
lorenzo.stoakes@...cle.com, snovitoll@...il.com, christophe.leroy@...roup.eu
Subject: Re: [PATCH v4 03/12] mm/kasan/sw_tags: don't initialize kasan if it's disabled
On Fri, Nov 28, 2025 at 4:34 AM Baoquan He <bhe@...hat.com> wrote:
>
This commit message is too empty :)
> Signed-off-by: Baoquan He <bhe@...hat.com>
> ---
> mm/kasan/sw_tags.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/mm/kasan/sw_tags.c b/mm/kasan/sw_tags.c
> index 6c1caec4261a..58edb68efc09 100644
> --- a/mm/kasan/sw_tags.c
> +++ b/mm/kasan/sw_tags.c
> @@ -40,6 +40,9 @@ void __init kasan_init_sw_tags(void)
> {
> int cpu;
>
Here and in other places where you check this flag, add a comment: "If
KASAN is disabled via command line, don't initialize it.".
> + if (kasan_arg_disabled)
> + return;
> +
> for_each_possible_cpu(cpu)
> per_cpu(prng_state, cpu) = (u32)get_cycles();
>
> --
> 2.41.0
>
Powered by blists - more mailing lists