linux-kernel - Re: [PATCH] lockdep: Print proper scenario if cross deadlock detected at acquisition time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170928135029.c3wnllu43h7f3xmn@tardis>
Date:   Thu, 28 Sep 2017 21:50:29 +0800
From:   Boqun Feng <boqun.feng@...il.com>
To:     Byungchul Park <byungchul.park@....com>
Cc:     linux-kernel@...r.kernel.org,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, kernel-team@....com
Subject: Re: [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

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)