From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: git pull request for tip/tracing/urgent
Date: Wed, 11 Feb 2009 09:49:19 +0100 [thread overview]
Message-ID: <20090211084919.GF21105@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0902101314440.23505@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> The bug that is fixed by this change can affect users. Most likely it will
> not, since the fault should never happen. But this is a protective
> mechanism, where if it does, that means there is a bug in the tracer.
>
> As you have previously told me, a bug in the tracer should never crash the
> kernel. Since the detection of a fault in the function graph tracer can
> lead to a kernel crash (without this change) I think this qualifies as
> something for 29.
Yeah, definitely so.
> -- Steve
>
>
> The following patch is in:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>
> branch: tip/tracing/urgent
>
>
> Steven Rostedt (1):
> tracing, x86: fix fixup section to return to original code
>
> ----
> arch/x86/kernel/ftrace.c | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
Pulled into tip:tracing/urgent, thanks Steve!
Ingo
prev parent reply other threads:[~2009-02-11 8:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 18:19 Steven Rostedt
2009-02-10 18:30 ` Frederic Weisbecker
2009-02-10 23:00 ` Steven Rostedt
2009-02-11 1:28 ` Frederic Weisbecker
2009-02-11 9:02 ` Ingo Molnar
2009-02-11 9:16 ` Tejun Heo
2009-02-11 9:53 ` Ingo Molnar
2009-02-12 1:24 ` H. Peter Anvin
2009-02-11 13:40 ` Frederic Weisbecker
2009-02-11 8:49 ` 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=20090211084919.GF21105@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
all inboxes | Powered by JetHome®