From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Borislav Petkov <bp@alien8.de>, Marco Elver <elver@google.com>,
Rong Chen <rong.a.chen@intel.com>,
kernel test robot <lkp@intel.com>,
"Li, Philip" <philip.li@intel.com>, x86-ml <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@chromium.org>
Subject: Re: [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e
Date: Tue, 15 Sep 2020 16:28:04 -0500 [thread overview]
Message-ID: <20200915212804.vvm7ovffqynkvi5a@treble> (raw)
In-Reply-To: <CAKwvOdmNzapwEo26m0soAR2OLFxOoERPKbKgvQ0bfoqjNkEVCg@mail.gmail.com>
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
next prev parent reply other threads:[~2020-09-15 21:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 13:42 [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e kernel test robot
2020-09-15 13:55 ` Borislav Petkov
2020-09-15 14:18 ` Rong Chen
2020-09-15 14:41 ` Borislav Petkov
2020-09-15 16:05 ` Borislav Petkov
2020-09-15 17:02 ` Josh Poimboeuf
2020-09-15 17:21 ` Borislav Petkov
2020-09-15 17:34 ` Borislav Petkov
2020-09-15 17:41 ` Nick Desaulniers
2020-09-15 18:01 ` Borislav Petkov
2020-09-15 18:04 ` Nick Desaulniers
2020-09-15 17:40 ` Nick Desaulniers
2020-09-15 18:09 ` Marco Elver
2020-09-16 8:30 ` peterz
2020-09-16 8:46 ` Marco Elver
2020-09-16 9:06 ` peterz
2020-09-16 9:33 ` Marco Elver
2020-09-16 18:22 ` Nick Desaulniers
2020-09-16 18:51 ` Marco Elver
2020-09-17 4:11 ` Fangrui Song
[not found] ` <333D40A0-4550-4309-9693-1ABA4AC75399@arm.com>
2020-09-17 11:04 ` Mark Rutland
2020-09-17 11:16 ` Daniel Kiss
2020-09-17 18:39 ` Josh Poimboeuf
2020-09-15 17:44 ` Nick Desaulniers
2020-09-15 20:12 ` Nick Desaulniers
2020-09-15 20:49 ` Borislav Petkov
2020-09-15 21:02 ` Josh Poimboeuf
2020-09-15 21:14 ` Borislav Petkov
2020-09-15 22:34 ` Nick Desaulniers
2020-09-16 7:03 ` Ilie Halip
2020-09-16 8:59 ` Marco Elver
2020-09-21 16:51 ` [tip: objtool/core] objtool: Ignore unreachable trap after call to noreturn functions tip-bot2 for Ilie Halip
2020-09-15 21:50 ` [tip:x86/seves] BUILD SUCCESS WITH WARNING e6eb15c9ba3165698488ae5c34920eea20eaa38e Arvind Sankar
2020-09-15 21:59 ` Nick Desaulniers
2020-09-15 22:44 ` Arvind Sankar
2020-09-16 11:34 ` Borislav Petkov
2020-09-16 18:28 ` Nick Desaulniers
2020-09-16 18:48 ` Borislav Petkov
2020-09-15 21:13 ` Nick Desaulniers
2020-09-15 21:28 ` Josh Poimboeuf [this message]
2020-09-15 23:35 ` Marco Elver
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=20200915212804.vvm7ovffqynkvi5a@treble \
--to=jpoimboe@redhat.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=clang-built-linux@googlegroups.com \
--cc=elver@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.com \
--cc=philip.li@intel.com \
--cc=rong.a.chen@intel.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.