[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAENh_SRw-L3UtBiz2xg_X4szdMJmNg118gL8f2g8gN5w6hc3Nw@mail.gmail.com>
Date: Mon, 16 Dec 2024 16:20:06 +0000
From: Matt Fleming <matt@...dmodwrite.com>
To: Uros Bizjak <ubizjak@...il.com>
Cc: Ingo Molnar <mingo@...nel.org>, Jakub Jelinek <jakub@...hat.com>, linux-kernel@...r.kernel.org,
kernel-team@...udflare.com
Subject: Re: CONFIG_KASAN triggers ASAN bug in GCC 13.3.0 and 14.1.0
On Sat, Dec 14, 2024 at 1:17 AM Uros Bizjak <ubizjak@...il.com> wrote:
>
> Does your config include CONFIG_UBSAN_BOOL=y ?
Yes, it does!
> There is a rare interaction between CONFIG_KASAN and CONFIG_UBSAN_BOOL
> (aka -fsanitize=bool), reported in [1] and fixed for gcc-14.2 in [2].
>
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111736#c42
>
> [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172
>
> Otherwise, please attach your .config, and I'll look into this issue.
Thanks. Disabling CONFIG_UBSAN_BOOL does indeed make the kernels boot again.
Should CONFIG_UBSAN_BOOL have a dependency on GCC 14.4+ ?
Powered by blists - more mailing lists