From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Jann Horn <jannh@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: objtool crashes on clang output (drivers/hwmon/pmbus/adm1275.o)
Date: Tue, 16 Jul 2019 18:03:36 -0500 [thread overview]
Message-ID: <20190716230336.y7nk24ybbwguio2s@treble> (raw)
In-Reply-To: <CAK8P3a2Vq+ojOZSefwziMhzU2SG+Bq6HDz2Ssjz7_BpVnMUu=A@mail.gmail.com>
On Wed, Jul 17, 2019 at 12:05:14AM +0200, Arnd Bergmann wrote:
> On Tue, Jul 16, 2019 at 10:24 PM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
> >
> > On Fri, Jul 12, 2019 at 1:41 PM Arnd Bergmann <arnd@arndb.de> wrote:
> > >
> > > On Fri, Jul 12, 2019 at 6:59 PM 'Nick Desaulniers' via Clang Built
> > > Linux <clang-built-linux@googlegroups.com> wrote:
> > > > > The issue still needs to get fixed in clang regardless. There are other
> > > > > noreturn functions in the kernel and this problem could easily pop back
> > > > > up.
> > > >
> > > > Sure, thanks for the report. Arnd, can you help us get a more minimal
> > > > test case to understand the issue better?
> > >
> > > I reduced it to this testcase:
> > >
> > > int a, b;
> > > void __reiserfs_panic(int, ...) __attribute__((noreturn));
> > > void balance_internal() {
> > > if (a)
> > > __reiserfs_panic(0, "", __func__, "", 2, __func__, a);
> > > if (b)
> > > __reiserfs_panic(0, "", __func__, "", 5, __func__, a, 0);
> > > }
> > >
> > > https://godbolt.org/z/Byfvmx
> >
> > Is this the same issue as Josh pointed out? IIUC, Josh pointed to a
> > jump destination that was past a `push %rbp`, and I don't see it in
> > your link. (Or, did I miss it?)
>
> I think it can be any push. The point is that the stack is different
> between the two branches leading up to the noreturn call.
Right.
--
Josh
next prev parent reply other threads:[~2019-07-16 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 12:40 Arnd Bergmann
2019-07-11 17:26 ` Josh Poimboeuf
2019-07-11 21:00 ` Arnd Bergmann
2019-07-11 21:04 ` Jann Horn
2019-07-11 21:29 ` Arnd Bergmann
2019-07-12 7:51 ` Arnd Bergmann
2019-07-12 13:57 ` Josh Poimboeuf
2019-07-12 14:19 ` Arnd Bergmann
2019-07-12 14:29 ` Josh Poimboeuf
2019-07-12 16:59 ` Nick Desaulniers
2019-07-12 20:40 ` Arnd Bergmann
2019-07-16 20:24 ` Nick Desaulniers
2019-07-16 22:05 ` Arnd Bergmann
2019-07-16 23:03 ` Josh Poimboeuf [this message]
2019-07-18 22:36 ` Nick Desaulniers
2019-07-18 23:20 ` Josh Poimboeuf
2019-07-11 23:20 ` 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=20190716230336.y7nk24ybbwguio2s@treble \
--to=jpoimboe@redhat.com \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®