[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200915212804.vvm7ovffqynkvi5a@treble>
Date: Tue, 15 Sep 2020 16:28:04 -0500
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Borislav Petkov <bp@...en8.de>, Marco Elver <elver@...gle.com>,
Rong Chen <rong.a.chen@...el.com>,
kernel test robot <lkp@...el.com>,
"Li, Philip" <philip.li@...el.com>, x86-ml <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Arnd Bergmann <arnd@...db.de>,
Kees Cook <keescook@...omium.org>
Subject: Re: [tip:x86/seves] BUILD SUCCESS WITH WARNING
e6eb15c9ba3165698488ae5c34920eea20eaa38e
On Tue, Sep 15, 2020 at 02:13:01PM -0700, Nick Desaulniers wrote:
> Triple checking what I wrote above; it looks like the randconfig had
> BOTH CONFIG_KASAN=y and CONFIG_UBSAN=y enabled. Aren't the sanitizers
> supposed to be mutually exclusive? If so, we should ensure that via
> kconfig these can't be selected together via randconfig.
No idea...
> Another peculiarity I noticed was that it seems that enabling
> CONFIG_UBSAN_TRAP=y doesn't allow me to select
> CONFIG_UBSAN_ALIGNMENT=y. Is that intentional? (Looks like it
> lib/Kconfig.ubsan:74).
That was done intentionally by Kees, it was putting traps in a lot of
weird places.
--
Josh
Powered by blists - more mailing lists