Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH] init: Add lockdep annotation to kthreadd_done completer
Date: Sat, 12 Aug 2023 16:02:10 +0200	[thread overview]
Message-ID: <1210dbf6-8bfe-9ea5-ba31-77c99e170817@gmx.de> (raw)
In-Reply-To: <180865b8-cba9-5676-ca7f-0865005f8af5@gmx.de>

Hi Andrew,

On 8/11/23 19:44, Helge Deller wrote:
> On 8/11/23 18:43, Andrew Morton wrote:
>> On Fri, 11 Aug 2023 18:04:22 +0200 Helge Deller <deller@gmx.de> wrote:
>>
>>> Add the missing lockdep annotation to avoid this warning:
>>>
>>>   INFO: trying to register non-static key.
>>>   The code is fine but needs lockdep annotation, or maybe
>>>   you didn't initialize this object before use?
>>>   turning off the locking correctness validator.
>>>   CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.5.0-rc5+ #681
>>>   Hardware name: 9000/785/C3700
>>>   Backtrace:
>>>    [<000000004030bcd0>] show_stack+0x74/0xb0
>>>    [<0000000041469c7c>] dump_stack_lvl+0x104/0x180
>>>    [<0000000041469d2c>] dump_stack+0x34/0x48
>>>    [<000000004040e5b4>] register_lock_class+0xd24/0xd30
>>>    [<000000004040c21c>] __lock_acquire.isra.0+0xb4/0xac8
>>>    [<000000004040cd60>] lock_acquire+0x130/0x298
>>>    [<000000004146df54>] _raw_spin_lock_irq+0x60/0xb8
>>>    [<0000000041472044>] wait_for_completion+0xa0/0x2d0
>>>    [<000000004146b544>] kernel_init+0x48/0x3a8
>>>    [<0000000040302020>] ret_from_kernel_thread+0x20/0x28
>>>
>>> ...
>>>
>>> --- a/init/main.c
>>> +++ b/init/main.c
>>> @@ -682,6 +682,8 @@ noinline void __ref __noreturn rest_init(void)
>>>       struct task_struct *tsk;
>>>       int pid;
>>>
>>> +    init_completion(&kthreadd_done);
>>> +
>>>       rcu_scheduler_starting();
>>>       /*
>>>        * We need to spawn init first so that it obtains pid 1, however
>>
>> This is pretty old code, as is the page_alloc_init_late() change.  Do
>> we know why this warning has just turned up lately?

[dropped Helge's assumptions that it's related to parisc's unusual
__ARCH_SPIN_LOCK_UNLOCKED_VAL value. It turned out to be wrong.

Now I was able to trace down why I see those lockdep warnings on parisc.
The short answer is:
On parisc the _initdata section lies outside of the usual kernel
_stext ... _end range. Lockdep calls static_obj() which currently assumes
that __initdata is inside that range and thus returns "false".
That's why lockdep then reports
	INFO: trying to register non-static key.
which is wrong.

Please drop those 3 lockdep patches from your mm-queue:

mm-add-lockdep-annotation-to-pgdat_init_all_done_comp-completer.patch
init-add-lockdep-annotation-to-kthreadd_done-completer.patch
watchdog-fix-lockdep-warning.patch

I'll send one single patch which fixes static_obj() instead.

Thanks,
Helge

      reply	other threads:[~2023-08-12 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 16:04 [PATCH] init: Add lockdep annotation to kthreadd_done completer Helge Deller
2023-08-11 16:43 ` Andrew Morton
2023-08-11 17:44   ` Helge Deller
2023-08-12 14:02     ` Helge Deller [this message]

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=1210dbf6-8bfe-9ea5-ba31-77c99e170817@gmx.de \
    --to=deller@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=rppt@kernel.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