mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
	<lkp@intel.com>, Linus Torvalds <torvalds@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] objtool fixes and updates
Date: Tue, 1 Apr 2025 08:38:09 +0800	[thread overview]
Message-ID: <Z+s1ceHFa0L1GMrn@rli9-mobl> (raw)
In-Reply-To: <rqwvk5a2ziu2hoklq45nrnw6n3k6akbd3k4tb5i2he4vty5dxt@gj4w2tsnj55o>

On Mon, Mar 31, 2025 at 03:17:51PM -0700, Josh Poimboeuf wrote:
> On Mon, Mar 31, 2025 at 06:10:45PM +0200, Ingo Molnar wrote:
> > > > This can be seen in the full report:
> > > > 
> > > >   https://lore.kernel.org/oe-kbuild-all/202503280703.OARM8SrY-lkp@intel.com/
> > > > 
> > > >   All warnings (new ones prefixed by >>):
> > > > 
> > > >      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
> > > >   >> arch/loongarch/kernel/traps.o: warning: objtool: show_stack+0xe0: skipping duplicate warning(s)
> > > > 
> > > > Note how '>>' is the new warning - the summary line added recently that 
> > > > suggests that there's more warnings. It appears to me the test-bot 
> > > > considers the other warnings old regressions, but I couldn't find any 
> > > > trace of them being reported before. Maybe they weren't Cc:-ed to lkml.
> > > > 
> > > > Or maybe these *are* all new warnings. I've Cc:-ed the LKP folks.
> > > 
> > > Hi Ingo and all, sorry for confusion, here only the line with >> is considered
> > > as new warning, due to the commit 0a7fb6f07e3a you mentioned.
> > 
> > Oh, so the loongson 'stack state mismatch' warnings started sometime in 
> > the past, but were never reported by the bot? Or were they reported 
> > somewhere? I'd like to discover the timeline of those warnings, if 
> > that's possible.
> 
> I believe those warnings were introduced a year ago with:
> 
>   cb8a2ef0848c ("LoongArch: Add ORC stack unwinder support")
> 
> but I wasn't able to find the original report.

Hi Ingo and Josh, for this cb8a2ef0848c commit, the bot has reported at [1]
but with a different randconfig and a different issue pattern. And the bot
didn't report new ones as it considered the bad commit was already reported.

	tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
	commit: cb8a2ef0848ca80d67d6d56e2df757cfdf6b3355 LoongArch: Add ORC stack unwinder support
	config: loongarch-randconfig-002-20240812 
(https://download.01.org/0day-ci/archive/20240812/202408120955.qls5oNQY-lkp@intel.com/config)

	WARNING: modpost: missing MODULE_DESCRIPTION() in net/ieee802154/6lowpan/ieee802154_6lowpan.o
	>> ERROR: modpost: "kvm_restore_lsx" [arch/loongarch/kvm/kvm.ko] undefined!
	>> ERROR: modpost: "kvm_restore_lasx" [arch/loongarch/kvm/kvm.ko] undefined!

Later, there's fix at [2], but seems it doesn't solve all possible issues since
the bot didn't report out explicitly.

[1] https://lore.kernel.org/oe-kbuild-all/202408120955.qls5oNQY-lkp@intel.com/
[2] https://lore.kernel.org/all/20240604150741.30252-1-xry111@xry111.site/

Thanks

> 
> -- 
> Josh

  reply	other threads:[~2025-04-01  0:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 21:18 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
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 [this message]
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+s1ceHFa0L1GMrn@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®