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: <rqwvk5a2ziu2hoklq45nrnw6n3k6akbd3k4tb5i2he4vty5dxt@gj4w2tsnj55o>
Date: Mon, 31 Mar 2025 15:17:51 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Philip Li <philip.li@...el.com>, 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 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.

-- 
Josh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ