From: Nathan Chancellor <nathan@kernel.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Klaus Kusche <klaus.kusche@computerix.info>,
peterz@infradead.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: "Bad or missing .orc_unwind table. Disabling unwinder." Clang 19 problem? 6.12.8 problem?
Date: Tue, 14 Jan 2025 02:51:59 -0700 [thread overview]
Message-ID: <20250114095159.GA1580513@ax162> (raw)
In-Reply-To: <20250113235835.vqgvb7cdspksy5dn@jpoimboe>
Hi Josh,
On Mon, Jan 13, 2025 at 03:58:35PM -0800, Josh Poimboeuf wrote:
> On Mon, Jan 13, 2025 at 01:41:24PM -0800, Josh Poimboeuf wrote:
> > On Mon, Jan 13, 2025 at 06:29:10PM +0100, Klaus Kusche wrote:
> > >
> > > Hello,
> > >
> > > I've submitted a bug report to kernel bugzilla,
> > > but it was closed with a hint that I should contact
> > > the maintainers and LKML.
> > >
> > > https://bugzilla.kernel.org/show_bug.cgi?id=219685
> > >
> > > You are listed as the maintainers for x86 stack unwinding.
> > > Any ideas about that problem before I submit it to LKML?
> > >
> > > Is it possibly related to
> > >
> > > https://bugzilla.kernel.org/show_bug.cgi?id=219686
> > >
> > > which appeared at the same time?
> > > Should it go to the clang maintainers?
> >
> > Hi Klaus,
> >
> > Thanks for reporting it. Indeed it's probably related to the build
> > warning:
> >
> > vmlinux.o: warning: objtool: start_unlink_intr+0xb7: can't find switch jump table
> >
> > It's probably a kernel bug, possibly triggered by the new compiler.
> > I'll see if I can recreate.
>
> [adding some folks]
Thanks for the CC, there was also an issue filed on our GitHub but I
have not had the chance to reply to it yet.
https://github.com/ClangBuiltLinux/linux/issues/2064
> Nathan, I think this is a Clang 19 issue, where one of the jump table
> entries is pointing past the end of the function. When we saw this in
> the past I think it was due to some leftover optimization, where the
> jump table entry ended up unused so it was harmless. Are you aware of
> any recent bugs in that area?
I am not aware of any recent bugs there but if you or Klaus have a
configuration file that triggers this, I would be happy to bisect LLVM
to see what change introduced it to give us a better understanding of
what is happening here.
> Maybe objtool should just ignore such entries?
This may be worth doing, especially in the face of the --Werror flag
that is being proposed.
Cheers,
Nathan
next prev parent reply other threads:[~2025-01-14 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b248a0fb-e182-42e3-abf5-83945ee992f6@computerix.info>
[not found] ` <20250113214122.g4lluwpzj3tnamx3@jpoimboe>
2025-01-13 23:58 ` "Bad or missing .orc_unwind table. Disabling unwinder." Clang 19 problem? 6.12.8 problem? Josh Poimboeuf
2025-01-14 9:51 ` Nathan Chancellor [this message]
2025-01-14 9:59 ` Klaus Kusche
2025-01-14 17:18 ` Nathan Chancellor
2025-05-29 13:56 ` 6.15.0: objtool "unexpected end of section" errors with clang 20.1.5 and lto Klaus Kusche
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=20250114095159.GA1580513@ax162 \
--to=nathan@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=klaus.kusche@computerix.info \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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 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.