From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/5] [GIP PULL] tracing/events/trace_stack: various fixes
Date: Mon, 8 Jun 2009 11:37:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0906081135320.9522@gandalf.stny.rr.com> (raw)
In-Reply-To: <20090607082257.GA16761@elte.hu>
[ Added Peter ]
On Sun, 7 Jun 2009, Ingo Molnar wrote:
> Testing tracer sched_switch: <6>Starting ring buffer hammer
> PASSED
> Testing tracer sysprof: PASSED
> Testing tracer function: PASSED
> Testing tracer irqsoff:
> =============================================
> PASSED
> Testing tracer preemptoff: PASSED
> Testing tracer preemptirqsoff: [ INFO: possible recursive locking detected ]
> PASSED
> Testing tracer branch: 2.6.30-rc8-tip-01972-ge5b9078-dirty #5760
> ---------------------------------------------
> rb_consumer/431 is trying to acquire lock:
> (&cpu_buffer->reader_lock){......}, at: [<c109eef7>] ring_buffer_reset_cpu+0x37/0x70
>
> but task is already holding lock:
> (&cpu_buffer->reader_lock){......}, at: [<c10a019e>] ring_buffer_consume+0x7e/0xc0
>
> other info that might help us debug this:
> 1 lock held by rb_consumer/431:
> #0: (&cpu_buffer->reader_lock){......}, at: [<c10a019e>] ring_buffer_consume+0x7e/0xc0
Yes this definitely looks like ftrace is tracing the ring buffer benchmark
test.
OK, how do I go about teaching lockdep that this reader lock is not the
same reader lock as the one being taken?
-- Steve
>
> stack backtrace:
> Pid: 431, comm: rb_consumer Not tainted 2.6.30-rc8-tip-01972-ge5b9078-dirty #5760
> Call Trace:
> [<c1070940>] validate_chain+0xa20/0x1000
> [<c1071240>] __lock_acquire+0x320/0x5f0
> [<c107159f>] lock_acquire+0x8f/0x120
> [<c109eef7>] ? ring_buffer_reset_cpu+0x37/0x70
> [<c1739c76>] _spin_lock_irqsave+0x56/0x70
> [<c109eef7>] ? ring_buffer_reset_cpu+0x37/0x70
> [<c109eef7>] ring_buffer_reset_cpu+0x37/0x70
> [<c10a596e>] tracing_reset+0x3e/0x80
> [<c109f4df>] ? rb_get_reader_page+0x11f/0x180
> [<c106c90b>] ? trace_hardirqs_off+0xb/0x10
> [<c10aa97f>] time_hardirqs_off+0xbf/0x110
> [<c109f4df>] ? rb_get_reader_page+0x11f/0x180
> [<c106c830>] trace_hardirqs_off_caller+0x20/0xf0
> [<c106c90b>] trace_hardirqs_off+0xb/0x10
> [<c109f4df>] rb_get_reader_page+0x11f/0x180
> [<c109f624>] rb_buffer_peek+0x24/0xe0
> [<c10a01ad>] ring_buffer_consume+0x8d/0xc0
> [<c10a1585>] ring_buffer_consumer_thread+0xa5/0x440
> [<c173a1c2>] ? _spin_unlock_irqrestore+0x62/0x80
> [<c10306be>] ? complete+0x4e/0x60
> [<c10a14e0>] ? ring_buffer_consumer_thread+0x0/0x440
> [<c105c1e2>] kthread+0x52/0x80
> [<c105c190>] ? kthread+0x0/0x80
> [<c10047cb>] kernel_thread_helper+0x7/0x10
next prev parent reply other threads:[~2009-06-08 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:17 Steven Rostedt
2009-06-03 15:17 ` [PATCH 1/5] tracing/trace_stack: fix the number of entries in the header Steven Rostedt
2009-06-03 15:17 ` [PATCH 2/5] tracing/events: fix output format of kernel stack Steven Rostedt
2009-06-03 15:17 ` [PATCH 3/5] tracing/events: fix output format of user stack Steven Rostedt
2009-06-03 15:17 ` [PATCH 4/5] tracing: fix multiple use of __print_flags and __print_symbolic Steven Rostedt
2009-06-03 15:17 ` [PATCH 5/5] tracing: add annotation to what type of stack trace is recorded Steven Rostedt
2009-06-05 14:52 ` [PATCH 0/5] [GIP PULL] tracing/events/trace_stack: various fixes Ingo Molnar
2009-06-07 8:22 ` Ingo Molnar
2009-06-08 15:37 ` Steven Rostedt [this message]
2009-06-08 16:18 ` Peter Zijlstra
2009-06-08 16:22 ` Steven Rostedt
2009-06-08 23:00 ` [PATCH][GIT PULL] ring-buffer: pass in lockdep class key for reader_lock Steven Rostedt
2009-06-09 11:20 ` Ingo Molnar
2009-06-09 11:44 ` Steven Rostedt
2009-06-09 12:03 ` Ingo Molnar
2009-06-09 14:52 ` [tip:tracing/core] " tip-bot for Peter Zijlstra
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=alpine.DEB.2.00.0906081135320.9522@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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®