From: "Paul E. McKenney" <paulmck@kernel.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: dmitry.torokhov@gmail.com, bentiss@kernel.org,
sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, linux-toolchains@vger.kernel.org
Subject: Re: [BUG] -next objtool build failure (bisected)
Date: Tue, 15 Oct 2024 11:57:24 -0700 [thread overview]
Message-ID: <688a88d8-0b40-486b-abc7-cf7c4a5f68d6@paulmck-laptop> (raw)
In-Reply-To: <20241015184507.hiepeqrjgcjssvoj@treble>
On Tue, Oct 15, 2024 at 01:45:07PM -0500, Josh Poimboeuf wrote:
> On Tue, Oct 15, 2024 at 11:10:11AM -0700, Paul E. McKenney wrote:
> > Hello!
> >
> > The next-20241011 release gets me build errors like the following:
> >
> > vmlinux.o: warning: objtool: fetch_item() falls through to next function
> >
> > Bisection leads me here:
> >
> > 61595012f280 ("HID: simplify code in fetch_item()")
> >
> > This diff looks inoffensive to me, but I get this error on this commit
> > and not on its predecessor.
> >
> > This build failure happens on quite a few different kernel configurations.
> > I bisected using this particular reproducer:
> >
> > tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --buildonly --configs SRCU-T
>
> The problem is likely this:
>
> + default:
> + unreachable();
>
> The unreachable() annotation by itself produces undefined behavior, as
> it will just fall off the edge of the function if the default case is
> ever executed.
>
> Better to do
>
> default:
> BUG();
>
> which makes the behavior defined.
And this fixes things for me, thank you!
Thanx, Paul
prev parent reply other threads:[~2024-10-15 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 18:10 [BUG] -next objtool build failure (bisected) Paul E. McKenney
2024-10-15 18:33 ` Dmitry Torokhov
2024-10-15 18:46 ` Paul E. McKenney
2024-10-15 18:45 ` Josh Poimboeuf
2024-10-15 18:57 ` Paul E. McKenney [this message]
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=688a88d8-0b40-486b-abc7-cf7c4a5f68d6@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=bentiss@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.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).