mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Byungchul Park <byungchul.park@lge.com>
Cc: linux-kernel@vger.kernel.org,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	kernel-team@lge.com
Subject: Re: [PATCH] lockdep: Print proper scenario if cross deadlock detected at acquisition time
Date: Thu, 28 Sep 2017 21:50:29 +0800	[thread overview]
Message-ID: <20170928135029.c3wnllu43h7f3xmn@tardis> (raw)
In-Reply-To: <20170927013145.GR5994@X58A-UD3R>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2017-09-28 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 12:52 Boqun Feng
2017-09-19 12:58 ` Boqun Feng
2017-09-26 13:55 ` Boqun Feng
2017-09-27  1:31 ` Byungchul Park
2017-09-28 13:50   ` Boqun Feng [this message]

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=20170928135029.c3wnllu43h7f3xmn@tardis \
    --to=boqun.feng@gmail.com \
    --cc=byungchul.park@lge.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®