[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f189719f-c7b9-e247-9251-8a336e41141d@alu.unizg.hr>
Date: Thu, 6 Jul 2023 07:02:11 +0200
From: Mirsad Todorovac <mirsad.todorovac@....unizg.hr>
To: Kees Cook <kees@...nel.org>, Kees Cook <keescook@...omium.org>
Cc: Guenter Roeck <linux@...ck-us.net>,
Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux LLVM <llvm@...ts.linux.dev>,
linux-kbuild@...r.kernel.org,
Linux Regressions <regressions@...ts.linux.dev>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
linux-hardening@...r.kernel.org
Subject: Re: [CRASH][BISECTED] 6.4.1 crash in boot
On 7/5/23 04:09, Kees Cook wrote:
>>>
>>> Hmm, is CONFIG_UBSAN_TRAP set?
>>
>> marvin@...iant:~/linux/kernel/linux_torvalds$ grep CONFIG_UBSAN_TRAP .config
>> CONFIG_UBSAN_TRAP=y
>
> Ah-ha! Turn that off please. With it off you will get much more useful reports from USBAN.
Done that. And it appears to work.
Great job.
There should be a way to store the earliest kernel messages while in the initrd phase, but
I can't think of any either ...
Have a nice day!
Best regards,
Mirsad Todorovac
Powered by blists - more mailing lists