public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/2] ftrace: fixes for tip
Date: Wed, 3 Dec 2008 17:15:34 +0100	[thread overview]
Message-ID: <20081203161534.GA6787@elte.hu> (raw)
In-Reply-To: <20081203160448.972919719@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> Ingo,
> 
> These two patches are fixes. The first cleans up the stack_trace
> output to print 0's for the return_to_handler function.
> 
> The second is the nasty race we have been hitting. My patches must
> have made the race window bigger for you since the bug was there
> before. It is a nasty race in the fork code. More info in the change log
> of that patch.
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: tip/devel
> 
> 
> Steven Rostedt (2):
>       trace: fix output of stack trace
>       ftrace: fix race in function graph during fork
> 
> ----
>  kernel/fork.c              |    9 ++++++---
>  kernel/trace/trace_stack.c |    5 ++++-
>  2 files changed, 10 insertions(+), 4 deletions(-)

pulled, thanks Steve! I think this should explain the crash i was seeing.

	Ingo

      parent reply	other threads:[~2008-12-03 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 16:04 [PATCH 0/2] ftrace: fixes for tip Steven Rostedt
2008-12-03 16:04 ` [PATCH 1/2] trace: fix output of stack trace Steven Rostedt
2008-12-03 16:04 ` [PATCH 2/2] ftrace: fix race in function graph during fork Steven Rostedt
2008-12-03 16:26   ` Frédéric Weisbecker
2008-12-03 16:15 ` 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=20081203161534.GA6787@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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