From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: linux-next: Tree for Mar 18 (objtool)
Date: Thu, 19 Mar 2020 12:33:26 -0500 [thread overview]
Message-ID: <20200319173326.oj4qs24x4ly5lrgt@treble> (raw)
In-Reply-To: <20200319173101.wufpymi7obhqgoqd@treble>
On Thu, Mar 19, 2020 at 12:31:05PM -0500, Josh Poimboeuf wrote:
> ... except the __builtin_trap() UD2 seems to be coming *after* the BUG
> UD2. Could it be the BUG UD2 itself which is convincing UBSAN to add
> the __builtin_trap()?
Actually I suspect it's the __builtin_unreachable() annotation which is
making UBSAN add the __builtin_trap()... because I don't see any double
UD2s for WARNs.
--
Josh
next prev parent reply other threads:[~2020-03-19 17:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 11:09 linux-next: Tree for Mar 18 Stephen Rothwell
2020-03-18 16:14 ` linux-next: Tree for Mar 18 (drivers/base/power/sysfs.c) Randy Dunlap
2020-03-19 3:20 ` Stephen Rothwell
2020-03-19 14:47 ` [PATCH net-next] sysfs: fix static inline declaration of sysfs_groups_change_owner() Christian Brauner
2020-03-19 16:19 ` Randy Dunlap
2020-03-20 4:17 ` David Miller
2020-03-18 16:48 ` linux-next: Tree for Mar 18 (objtool) Randy Dunlap
2020-03-18 16:55 ` Josh Poimboeuf
2020-03-18 18:23 ` Josh Poimboeuf
2020-03-18 20:05 ` Peter Zijlstra
2020-03-19 11:12 ` Peter Zijlstra
2020-03-19 17:31 ` Josh Poimboeuf
2020-03-19 17:33 ` Josh Poimboeuf [this message]
2020-03-19 17:40 ` Josh Poimboeuf
2020-03-19 17:45 ` Josh Poimboeuf
2020-03-20 8:26 ` Peter Zijlstra
2020-03-20 18:35 ` Kees Cook
2020-03-24 16:44 ` Josh Poimboeuf
2020-03-24 18:18 ` Kees Cook
2020-03-24 22:24 ` Josh Poimboeuf
2020-03-26 5:57 ` Kees Cook
2020-03-26 16:31 ` Josh Poimboeuf
2020-03-26 18:36 ` Kees Cook
2020-03-27 3:55 ` Josh Poimboeuf
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=20200319173326.oj4qs24x4ly5lrgt@treble \
--to=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).