linux-kernel - Re: [PATCH] lockdep: Fix static memory detection even more

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: <f8ca4666-1a64-49fe-afa7-47e72c82ef9e@leemhuis.info>
Date:   Sun, 10 Sep 2023 13:20:16 +0200
From:   "Linux regression tracking #adding (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Guenter Roeck <linux@...ck-us.net>, Helge Deller <deller@....de>
Cc:     linux-kernel@...r.kernel.org, linux-parisc@...r.kernel.org,
        Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH] lockdep: Fix static memory detection even more

[side notes:
* mail has a reduced set of recipients
* fix is in the works, but add it to the tracking, as rc1 is due
* just in case it was missed: culprit made it to various stable series]

[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]

On 03.09.23 21:36, Guenter Roeck wrote:
> 
> On Sat, Aug 12, 2023 at 05:48:52PM +0200, Helge Deller wrote:
>> On the parisc architecture, lockdep reports for all static objects which
>> are in the __initdata section (e.g. "setup_done" in devtmpfs,
>> "kthreadd_done" in init/main.c) this warning:
>>
>> 	INFO: trying to register non-static key.
>>
> [...]
>> Signed-off-by: Helge Deller <deller@....de>
>> Fixes: bac59d18c701 ("x86/setup: Fix static memory detection")
> 
> On loongarch, this patch results in the following backtrace.
> [...]> # first bad commit: [0a6b58c5cd0dfd7961e725212f0fc8dfc5d96195]
lockdep: fix static memory detection even more

Thanks for the report. To be sure the issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
tracking bot:

#regzbot ^introduced 0a6b58c5cd0dfd7961e725212f0fc8dfc5d961
#regzbot title lockdep: backtrace on loongarch
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.