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: <reikdbyyvobo5vu2r4n55znptefmbcvcxoovrcenwatu32vo3e@nivvxsxwbvuk>
Date: Mon, 31 Mar 2025 08:29:41 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, 
	linux-kernel@...r.kernel.org, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [GIT PULL] objtool fixes and updates

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 ;-)

>     `-- 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.

-- 
Josh