From: Ingo Molnar <mingo@kernel.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] objtool fixes and updates
Date: Mon, 31 Mar 2025 11:39:13 +0200 [thread overview]
Message-ID: <Z-piwUbLx-OitJrv@gmail.com> (raw)
In-Reply-To: <sdjfftubzcheo3dpejml54t6axfjfrd7pk6mnbkpb2n7alpfzn@6l6bldqfturq>
* Josh Poimboeuf <jpoimboe@kernel.org> wrote:
> On Mon, Mar 31, 2025 at 01:13:55AM +0200, Borislav Petkov wrote:
> > On Sun, Mar 30, 2025 at 03:19:40PM -0700, Linus Torvalds wrote:
> > > On Sat, 29 Mar 2025 at 08:33, Borislav Petkov <bp@alien8.de> wrote:
> > > >
> > > > Btw, test bot complains:
> > > >
> > > > https://lore.kernel.org/r/202503292202.Sge7ZEUc-lkp@intel.com
> > >
> > > That's not a very helpful error message
> >
> > I found this:
> >
> > https://lore.kernel.org/r/202503280703.OARM8SrY-lkp@intel.com
> >
> > which looks like the original report.
> >
> > Looks unsolved yet...
>
> The "new" warning is just the "skipping duplicate warning", which was
> already merged with commit 0a7fb6f07e3a ("objtool: Increase per-function
> WARN_FUNC() rate limit"). So none of the warnings are specific to this
> pull request.
>
> Tiezhu, can you please look at this warning?
>
> arch/loongarch/kernel/traps.o: warning: objtool: show_stack+0xe0: stack state mismatch: reg1[22]=-1+0 reg2[22]=-2-160
> arch/loongarch/kernel/traps.o: warning: objtool: show_stack+0xe0: stack state mismatch: reg1[23]=-1+0 reg2[23]=-2-152
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:
`-- 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.
Or delay the reporting to until the entire pass is finished, and
output something like:
warning: objtool: show_stack+0xe0: stack state mismatch: reg1[22]=-1+0 reg2[22]=-2-160 [2+ more warnings]
Note: we shouldn't output the real warning count - just that it's
multiple warnings that might or might not be resolved by fixing the
primary warning.
Or something like that.
Thanks,
Ingo
============>
tools/objtool/include/objtool/warn.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/tools/objtool/include/objtool/warn.h b/tools/objtool/include/objtool/warn.h
index b29ac144e4f5..69dd29a3c267 100644
--- a/tools/objtool/include/objtool/warn.h
+++ b/tools/objtool/include/objtool/warn.h
@@ -57,7 +57,7 @@ static inline char *offstr(struct section *sec, unsigned long offset)
free(_str); \
})
-#define WARN_LIMIT 2
+#define WARN_LIMIT 1
#define WARN_INSN(insn, format, ...) \
({ \
@@ -69,8 +69,6 @@ static inline char *offstr(struct section *sec, unsigned long offset)
if (_insn->sym) \
_insn->sym->warnings++; \
} else if (_insn->sym && _insn->sym->warnings == WARN_LIMIT) { \
- WARN_FUNC("skipping duplicate warning(s)", \
- _insn->sec, _insn->offset); \
_insn->sym->warnings++; \
} \
})
next prev parent reply other threads:[~2025-03-31 9:39 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 [this message]
2025-03-31 15:29 ` Josh Poimboeuf
2025-03-31 16:07 ` Ingo Molnar
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-piwUbLx-OitJrv@gmail.com \
--to=mingo@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.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 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.