linux-kernel - Re: [GIT PULL] objtool fixes and updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z+s1ceHFa0L1GMrn@rli9-mobl>
Date: Tue, 1 Apr 2025 08:38:09 +0800
From: Philip Li <philip.li@...el.com>
To: Josh Poimboeuf <jpoimboe@...nel.org>
CC: Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
	<lkp@...el.com>, Linus Torvalds <torvalds@...ux-foundation.org>,
	<linux-kernel@...r.kernel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>, Andrew Morton
	<akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] objtool fixes and updates

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