Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1741566

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

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH] lockdep: Print proper scenario if cross deadlock  detected at acquisition time Byungchul Park <byungchul.park@lge.com> - 2017-09-27 03:40 +0200
  Re: [PATCH] lockdep: Print proper scenario if cross deadlock  detected at acquisition time Boqun Feng <boqun.feng@gmail.com> - 2017-09-28 15:50 +0200

csiph-web