lkml.org 
[lkml]   [2019]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: "locking/lockdep: Consolidate lock usage bit initialization" is buggy
Thanks for the further validation.

On Fri, 7 Jun 2019 at 22:14, Qian Cai <cai@lca.pw> wrote:
> Reverted the commit on the top of linux-next fixed the issue.
>
> With the commit (triggering the warning
> DEBUG_LOCKS_WARN_ON(debug_atomic_read(nr_unused_locks) != nr_unused)),
>
> # cat /proc/lockdep_stats
> lock-classes: 1110 [max: 8192]
> stack-trace entries: 0 [max: 524288]
> combined max dependencies: 1
> uncategorized locks: 0
> unused locks: 1110
> max locking depth: 14
> debug_locks: 0
>
> Without the commit (no warning),
>
> # cat /proc/lockdep_stats
> lock-classes: 1110 [max: 8192]
> stack-trace entries: 9932 [max: 524288]
> combined max dependencies: 1
> uncategorized locks: 1113
> unused locks: 0
> max locking depth: 14
> debug_locks: 1

Then it is obviously we are talking on different things; then it is
obviously a configuration problem. Fix will be posted soon.

Sorry the bug.

Thanks,
Yuyang

\
 
 \ /
  Last update: 2019-06-10 04:23    [W:0.043 / U:3.664 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site