Re: [PATCH] locking/lockdep: Report comm/pid/timestamp information

2018-07-09 Thread Eugeniu Rosca
On Mon, Jul 09, 2018 at 10:31:18AM +0200, Peter Zijlstra wrote: > On Mon, Jul 09, 2018 at 02:57:25AM +0200, Eugeniu Rosca wrote: > > diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h > > index 6fc77d4dbdcd..eeed7ea2e198 100644 > > --- a/include/linux/lockdep.h > > +++

Re: [PATCH] locking/lockdep: Report comm/pid/timestamp information

2018-07-09 Thread Eugeniu Rosca
On Mon, Jul 09, 2018 at 10:31:18AM +0200, Peter Zijlstra wrote: > On Mon, Jul 09, 2018 at 02:57:25AM +0200, Eugeniu Rosca wrote: > > diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h > > index 6fc77d4dbdcd..eeed7ea2e198 100644 > > --- a/include/linux/lockdep.h > > +++

Re: [PATCH] locking/lockdep: Report comm/pid/timestamp information

2018-07-09 Thread Peter Zijlstra
On Mon, Jul 09, 2018 at 02:57:25AM +0200, Eugeniu Rosca wrote: > diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h > index 6fc77d4dbdcd..eeed7ea2e198 100644 > --- a/include/linux/lockdep.h > +++ b/include/linux/lockdep.h > @@ -186,6 +186,10 @@ struct lock_list { > struct

Re: [PATCH] locking/lockdep: Report comm/pid/timestamp information

2018-07-09 Thread Peter Zijlstra
On Mon, Jul 09, 2018 at 02:57:25AM +0200, Eugeniu Rosca wrote: > diff --git a/include/linux/lockdep.h b/include/linux/lockdep.h > index 6fc77d4dbdcd..eeed7ea2e198 100644 > --- a/include/linux/lockdep.h > +++ b/include/linux/lockdep.h > @@ -186,6 +186,10 @@ struct lock_list { > struct

[PATCH] locking/lockdep: Report comm/pid/timestamp information

2018-07-08 Thread Eugeniu Rosca
Analyzing the "circular locking dependency" splat [2], I can see the following skeleton/pattern: is trying to acquire lock X. *same* has previously acquired lock Y. lock Y depends on lock X (hence chance for deadlock). Print lock dependency chain: -> #N

[PATCH] locking/lockdep: Report comm/pid/timestamp information

2018-07-08 Thread Eugeniu Rosca
Analyzing the "circular locking dependency" splat [2], I can see the following skeleton/pattern: is trying to acquire lock X. *same* has previously acquired lock Y. lock Y depends on lock X (hence chance for deadlock). Print lock dependency chain: -> #N