From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>
Subject: Re: [PATCH 0/6] ftrace: port to the new ring_buffer
Date: Tue, 30 Sep 2008 08:04:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0809300801500.30533@gandalf.stny.rr.com> (raw)
In-Reply-To: <20080930082302.GA2852@elte.hu>
On Tue, 30 Sep 2008, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > very nice! I'd expect breakages and complications too so i
> > restructured tip/tracing/* a bit: firstly i created a tip/tracing/core
> > append-only merge branch which collects all the known-robust bits.
> > Then i created a new branch for your new generic ring-buffer feature:
> > tip/tracing/ring-buffer, and applied your patches. I've started
> > testing it.
>
> -tip testing found that tip/tracing/ring-buffer causes a new lockdep
> splat:
>
> [ 0.000000] Linux version 2.6.27-rc8-tip-00915-g8cb18a9-dirty (mingo@dione)
> (gcc version 4.2.3) #37501 SMP Tue Sep 30 10:10:10 CEST 2008
> [...]
> [ 0.268001] calling tracer_alloc_buffers+0x0/0x1e5 @ 1
> [ 0.270983] ------------[ cut here ]------------
> [ 0.271100] WARNING: at kernel/lockdep.c:2880 check_flags+0x63/0x179()
> [ 0.271219] Modules linked in:
> [ 0.271356] Pid: 1, comm: swapper Not tainted 2.6.27-rc8-tip-00915-g8cb18a9-dirty #37501
> [ 0.271563] Call Trace:
> [ 0.271678] [<ffffffff80271d2b>] warn_on_slowpath+0x5d/0x84
> [ 0.271797] [<ffffffff80295973>] ? __lock_acquire+0xba4/0xbc5
> [ 0.271916] [<ffffffff8029266d>] ? __raw_spin_is_locked+0x17/0x1a
> [ 0.272001] [<ffffffff802929cc>] ? graph_unlock+0x79/0x7e
> [ 0.272001] [<ffffffff8029449f>] ? mark_lock+0x1c/0x361
> [ 0.272001] [<ffffffff8029483a>] ? mark_held_locks+0x56/0x71
> [ 0.272001] [<ffffffff802cbb77>] ? time_hardirqs_off+0x12/0x26
> [ 0.272001] [<ffffffff802934f1>] ? trace_hardirqs_off_caller+0x21/0xc2
I don't even need to look at the configs. There's places I still used the
"raw_local_irq_save" and that is what in the past has caused this issue.
I'll go and remove those.
-- Steve
prev parent reply other threads:[~2008-09-30 12:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 3:02 [PATCH 0/6] ftrace: port to the new ring_buffer Steven Rostedt
2008-09-30 3:02 ` [PATCH 1/6] ftrace: give time for wakeup test to run Steven Rostedt
2008-09-30 3:02 ` [PATCH 2/6] Unified trace buffer Steven Rostedt
2008-09-30 9:45 ` Ingo Molnar
2008-09-30 11:53 ` Ingo Molnar
2008-09-30 12:06 ` Steven Rostedt
2008-09-30 3:02 ` [PATCH 3/6] ring_buffer: add paranoid check for buffer page Steven Rostedt
2008-09-30 3:02 ` [PATCH 4/6] ring_buffer: reset buffer page when freeing Steven Rostedt
2008-09-30 3:02 ` [PATCH 5/6] ftrace: make work with new ring buffer Steven Rostedt
2008-09-30 3:02 ` [PATCH 6/6] ftrace: take advantage of variable length entries Steven Rostedt
2008-09-30 17:33 ` Pekka Paalanen
2008-09-30 17:45 ` Steven Rostedt
2008-10-01 4:42 ` Steven Rostedt
2008-10-01 7:54 ` Ingo Molnar
2008-10-01 14:52 ` Steven Rostedt
2008-10-01 14:52 ` [PATCH] ftrace: type cast verifier Steven Rostedt
2008-10-01 17:42 ` Ingo Molnar
2008-10-01 17:47 ` Ingo Molnar
2008-09-30 7:45 ` [PATCH 0/6] ftrace: port to the new ring_buffer Ingo Molnar
2008-09-30 8:23 ` Ingo Molnar
2008-09-30 8:30 ` Ingo Molnar
2008-09-30 9:13 ` Ingo Molnar
2008-09-30 12:04 ` Steven Rostedt
2008-09-30 12:04 ` Steven Rostedt [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=alpine.DEB.1.10.0809300801500.30533@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).