From: Ingo Molnar <mingo@kernel.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] objtool fixes and updates
Date: Mon, 31 Mar 2025 18:07:05 +0200 [thread overview]
Message-ID: <Z-q9qbTGxNGICG4c@gmail.com> (raw)
In-Reply-To: <reikdbyyvobo5vu2r4n55znptefmbcvcxoovrcenwatu32vo3e@nivvxsxwbvuk>
* Josh Poimboeuf <jpoimboe@kernel.org> wrote:
> On Mon, Mar 31, 2025 at 11:39:13AM +0200, Ingo Molnar wrote:
> > I'm wondering why LKP didn't pick up the primary warning, only the
> > final warning that skips duplicate warnings, which is kinda totally
> > useless in isolation:
>
> At least it alerted us to the other loongarch warnings we hadn't seen ;-)
There's that :-)
> > `-- arch-loongarch-kernel-traps.o:warning:objtool:show_stack:skipping-duplicate-warning(s)
> >
> > Maybe we should just do what is below - output a single warning, a bit
> > like lockdep.
>
> Yeah, "skipping duplicate warnings" isn't technically a warning so it
> probably shouldn't be presented as one.
>
> I'll just revert 0a7fb6f07e3a and go back to the simple "one warning
> per function" which worked fine before.
Thanks! Our experience with lockdep is that the fewer warnings per
build/bootup, the better: the value of secondary warnings is
diminishing, sometimes even negative.
It might even be OK to generate just one objtool warning per .o file.
Ingo
next prev parent reply other threads:[~2025-03-31 16:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 21:18 [GIT PULL] objtool fixes and updates Ingo Molnar
2025-03-29 15:32 ` Borislav Petkov
2025-03-30 22:19 ` Linus Torvalds
2025-03-30 23:13 ` Borislav Petkov
2025-03-31 1:39 ` Josh Poimboeuf
2025-03-31 9:39 ` Ingo Molnar
2025-03-31 15:29 ` Josh Poimboeuf
2025-03-31 16:07 ` Ingo Molnar [this message]
2025-03-31 22:19 ` Josh Poimboeuf
2025-04-01 7:58 ` Ingo Molnar
2025-03-31 11:55 ` Ingo Molnar
2025-03-31 12:31 ` Philip Li
2025-03-31 12:36 ` Borislav Petkov
2025-03-31 12:44 ` Philip Li
2025-03-31 12:49 ` Borislav Petkov
2025-03-31 13:27 ` Philip Li
2025-03-31 16:10 ` Ingo Molnar
2025-03-31 22:17 ` Josh Poimboeuf
2025-04-01 0:38 ` Philip Li
2025-04-01 2:05 ` Tiezhu Yang
2025-04-01 4:15 ` Josh Poimboeuf
2025-04-01 6:12 ` Tiezhu Yang
2025-04-02 17:48 ` pr-tracker-bot
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=Z-q9qbTGxNGICG4c@gmail.com \
--to=mingo@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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