lkml.org 
[lkml]   [2017]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] lockdep: Print proper scenario if cross deadlock detected at acquisition time
On Wed, Sep 27, 2017 at 01:31:45AM +0000, Byungchul Park wrote:
>
> Sometimes, it gives a wrong scenario. For example:
>
> lock target
> lock source
> lock parent
> lock target
> lock parent of parent
> lock parent
>
> lock parent of parent
> unlock source
>
> We should consider this scenario as well so the report is always true
> generally.
>

Right, let me think about a proper way to do this.

Regards,
Boqun

> > + printk(KERN_CONT ");\n");
> > + printk("\n *** DEADLOCK ***\n\n");
> > } else {
> > printk(" Possible unsafe locking scenario:\n\n");
> > printk(" CPU0 CPU1\n");
> > --
> > 2.14.1
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2017-09-28 15:50    [W:0.063 / U:0.280 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site