From: Bart Van Assche <bvanassche@acm.org>
To: lkp@lists.01.org
Subject: Re: cdbeb78c7a ("kernel/workqueue: Use dynamic lockdep keys for .."): WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:1002 lockdep_register_key
Date: Mon, 17 Dec 2018 09:32:57 -0800 [thread overview]
Message-ID: <1545067977.185366.436.camel@acm.org> (raw)
In-Reply-To: <5c17230f.mbgTPR4404Mp8abU%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
On Mon, 2018-12-17 at 12:16 +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://github.com/bvanassche/linux for-next
>
> commit cdbeb78c7a2e34af6d6cc5d3570a585a23eea8e9
> Author: Bart Van Assche <bvanassche@acm.org>
> AuthorDate: Fri Nov 9 09:53:31 2018 -0800
> Commit: Bart Van Assche <bvanassche@acm.org>
> CommitDate: Fri Dec 14 11:24:37 2018 -0800
>
> kernel/workqueue: Use dynamic lockdep keys for workqueues
>
> [ ... ]
>
> 60e521015c locking/lockdep: Add support for dynamic keys
> cdbeb78c7a kernel/workqueue: Use dynamic lockdep keys for workqueues
> 9294000d6d IB/srp: Drain the send queue before destroying a QP
> +-----------------------------------------------------------+------------+------------+---------------------+
> > | 60e521015c | cdbeb78c7a | bvanassche/for-next |
>
> +-----------------------------------------------------------+------------+------------+---------------------+
> > boot_successes | 915 | 305 | 0 |
> > boot_failures | 1 | 7 | 310 |
> > INFO:rcu_preempt_self-detected_stall_on_CPU | 1 | | |
> > EIP:smp_call_function_single | 1 | | |
> > BUG:kernel_hang_in_boot-around-mounting-root_stage | 1 | | |
> > WARNING:at_kernel/locking/lockdep.c:#lockdep_register_key | 0 | 7 | |
> > EIP:lockdep_register_key | 0 | 7 | |
> > WARNING:kernel_stack | 0 | 0 | 310 |
>
> +-----------------------------------------------------------+------------+------------+---------------------+
The "WARNING:at_kernel/locking/lockdep.c:#lockdep_register_key" warnings have
already been removed from my branch so I think this report can be ignored.
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bvanassche@acm.org>
To: kernel test robot <lkp@intel.com>
Cc: LKP <lkp@01.org>, linux-kernel@vger.kernel.org
Subject: Re: cdbeb78c7a ("kernel/workqueue: Use dynamic lockdep keys for .."): WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:1002 lockdep_register_key
Date: Mon, 17 Dec 2018 09:32:57 -0800 [thread overview]
Message-ID: <1545067977.185366.436.camel@acm.org> (raw)
In-Reply-To: <5c17230f.mbgTPR4404Mp8abU%lkp@intel.com>
On Mon, 2018-12-17 at 12:16 +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://github.com/bvanassche/linux for-next
>
> commit cdbeb78c7a2e34af6d6cc5d3570a585a23eea8e9
> Author: Bart Van Assche <bvanassche@acm.org>
> AuthorDate: Fri Nov 9 09:53:31 2018 -0800
> Commit: Bart Van Assche <bvanassche@acm.org>
> CommitDate: Fri Dec 14 11:24:37 2018 -0800
>
> kernel/workqueue: Use dynamic lockdep keys for workqueues
>
> [ ... ]
>
> 60e521015c locking/lockdep: Add support for dynamic keys
> cdbeb78c7a kernel/workqueue: Use dynamic lockdep keys for workqueues
> 9294000d6d IB/srp: Drain the send queue before destroying a QP
> +-----------------------------------------------------------+------------+------------+---------------------+
> > | 60e521015c | cdbeb78c7a | bvanassche/for-next |
>
> +-----------------------------------------------------------+------------+------------+---------------------+
> > boot_successes | 915 | 305 | 0 |
> > boot_failures | 1 | 7 | 310 |
> > INFO:rcu_preempt_self-detected_stall_on_CPU | 1 | | |
> > EIP:smp_call_function_single | 1 | | |
> > BUG:kernel_hang_in_boot-around-mounting-root_stage | 1 | | |
> > WARNING:at_kernel/locking/lockdep.c:#lockdep_register_key | 0 | 7 | |
> > EIP:lockdep_register_key | 0 | 7 | |
> > WARNING:kernel_stack | 0 | 0 | 310 |
>
> +-----------------------------------------------------------+------------+------------+---------------------+
The "WARNING:at_kernel/locking/lockdep.c:#lockdep_register_key" warnings have
already been removed from my branch so I think this report can be ignored.
Bart.
next prev parent reply other threads:[~2018-12-17 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 4:16 cdbeb78c7a ("kernel/workqueue: Use dynamic lockdep keys for .."): WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:1002 lockdep_register_key kernel test robot
2018-12-17 4:16 ` kernel test robot
2018-12-17 17:32 ` Bart Van Assche [this message]
2018-12-17 17:32 ` Bart Van Assche
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=1545067977.185366.436.camel@acm.org \
--to=bvanassche@acm.org \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.