mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dhaval Giani <dhaval.giani@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] lockdep: Show up to three levels for a deadlock scenario
Date: Tue, 19 Dec 2017 18:29:37 +0100	[thread overview]
Message-ID: <20171219172937.uiwnnkde5iuw3mva@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20171219121124.79bca79b@gandalf.local.home>

On Tue, Dec 19, 2017 at 12:11:24PM -0500, Steven Rostedt wrote:
> On Tue, 19 Dec 2017 18:07:16 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
> 
> > On Tue, Dec 19, 2017 at 11:52:38AM -0500, Steven Rostedt wrote:
> > > Then I suggest that you can either take my patch to improve the
> > > visual or remove the visual completely, as nobody cares about it.  
> > 
> > Doesn't apply as is; but can you at least make it shut up if the chain
> > is longer than you support?
> 
> I can add that.
> 
> > 
> > It's really annoying if it shows the AB-BA graphics when you're staring
> > at a 5-6 lock scenario.
> 
> I could also make it dynamic, to handle the entire chain. But it will
> make it longer.

Makes it too wide I think, people already have a problem quoting the
thing in emails (wrap mangles like stupid).

Take the below while you're poking at it.. that should hopefully make
the #0 stacktrace go away.

diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
index 5fa1324a4f29..6aa431c4ad99 100644
--- a/kernel/locking/lockdep.c
+++ b/kernel/locking/lockdep.c
@@ -1085,7 +1085,8 @@ print_circular_bug_entry(struct lock_list *target, int depth)
 	printk("\n-> #%u", depth);
 	print_lock_name(target->class);
 	printk(KERN_CONT ":\n");
-	print_stack_trace(&target->trace, 6);
+	if (depth)
+		print_stack_trace(&target->trace, 6);
 
 	return 0;
 }

      reply	other threads:[~2017-12-19 17:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 17:38 Steven Rostedt
2017-12-14 17:59 ` Peter Zijlstra
2017-12-14 18:19   ` Steven Rostedt
2017-12-19 16:30   ` Dhaval Giani
2017-12-19 16:46     ` Peter Zijlstra
2017-12-19 16:52       ` Steven Rostedt
2017-12-19 16:54         ` Dhaval Giani
2017-12-19 17:10           ` Steven Rostedt
2017-12-19 17:07         ` Peter Zijlstra
2017-12-19 17:11           ` Steven Rostedt
2017-12-19 17:29             ` Peter Zijlstra [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=20171219172937.uiwnnkde5iuw3mva@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhaval.giani@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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®