All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: bentiss@kernel.org, sfr@canb.auug.org.au,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	linux-toolchains@vger.kernel.org, jpoimboe@kernel.org
Subject: Re: [BUG] -next objtool build failure (bisected)
Date: Tue, 15 Oct 2024 11:33:11 -0700	[thread overview]
Message-ID: <Zw61Z8xBhe1oJ_-W@google.com> (raw)
In-Reply-To: <fe8c909e-bf02-4466-b3eb-0a4747df32e3@paulmck-laptop>

Hi Paul,

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
> 
> Thoughts?

I just added you to another thread where Nathan proposed a couple of
solutions:

https://lore.kernel.org/r/20241010222451.GA3571761@thelio-3990X

Thanks.

-- 
Dmitry

  reply	other threads:[~2024-10-15 18:33 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 [this message]
2024-10-15 18:46   ` Paul E. McKenney
2024-10-15 18:45 ` Josh Poimboeuf
2024-10-15 18:57   ` Paul E. McKenney

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=Zw61Z8xBhe1oJ_-W@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-toolchains@vger.kernel.org \
    --cc=paulmck@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 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.