From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/2] ftrace updates for 2.6.28
Date: Tue, 11 Nov 2008 09:23:47 +0100 [thread overview]
Message-ID: <20081111082347.GB29901@elte.hu> (raw)
In-Reply-To: <20081111025808.946638585@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> The following patches are in:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>
> branch: devel
>
> Steven Rostedt (2):
> ftrace: disable tracing on resize
> ring-buffer: prevent infinite looping on time stamping
>
> ----
> kernel/trace/ring_buffer.c | 2 +-
> kernel/trace/trace.c | 17 ++++++++++++++++-
> 2 files changed, 17 insertions(+), 2 deletions(-)
pulled into tip/tracing/urgent, thanks Steve!
> The following patches are needed for 2.6.28. The first one solves a
> bug where the resizing of the buffer array was not protected against
> modifications by ftrace.
>
> The second patch solves an issue tha Thomas Gleixner was seeing
> where the tracer would detect the infinite recursion too easily by
> tracing the timer code. This patch prevents the loop from happening
> and still does not lose any trace entries.
>
> The changes caused by these patches are low in risk, but I would
> still like to put them through linux-next before passing them off to
> Linus.
>
> Note, these changes are based against Linus's mainline and not tip.
> Also note that the branch in this tree is "devel" and not
> "tip/devel".
that's OK. I resolved the (trivial) conflict with pending changes in
tip/tracing/ftrace and pushed out a new ftrace integration branch
towards linux-next.
Ingo
prev parent reply other threads:[~2008-11-11 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 2:58 [PATCH 0/2] ftrace updates for 2.6.28 Steven Rostedt
2008-11-11 2:58 ` [PATCH 1/2] ftrace: disable tracing on resize Steven Rostedt
2008-11-11 3:18 ` Steven Rostedt
2008-11-12 19:56 ` Pekka Paalanen
2008-11-12 20:32 ` Steven Rostedt
2008-11-13 0:03 ` Steven Rostedt
2008-11-11 2:58 ` [PATCH 2/2] ring-buffer: prevent infinite looping on time stamping Steven Rostedt
2008-11-11 3:27 ` [PATCH 0/2] ftrace updates for 2.6.28 Steven Rostedt
2008-11-11 8:23 ` Ingo Molnar [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=20081111082347.GB29901@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--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).