From: Steven Rostedt <rostedt@goodmis.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Question about -rc and stable patches
Date: Mon, 3 Mar 2014 17:45:32 -0500 [thread overview]
Message-ID: <20140303174532.7cb8f31e@gandalf.local.home> (raw)
In-Reply-To: <20140303224104.GA26031@kroah.com>
On Mon, 3 Mar 2014 14:41:04 -0800
Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Mon, Mar 03, 2014 at 05:28:06PM -0500, Steven Rostedt wrote:
> > Hi Linus and Greg,
> >
> > Recently I have been sent patches that fix a bug in the enabling of
> > ftrace function tracer, where if something goes wrong with the
> > enabling (or disabling), it can cause a crash of the computer.
> >
> > Now, my question is, the bug requires something to go wrong at a point
> > where I've never seen it go wrong before. But if you inject a problem
> > (code that makes it fail on the 1000th iteration), sure enough, the
> > recovery is not correct and the machine crashes.
>
> What exactly do you mean by "inject a problem"? What kind of
> permissions does that require to do?
Modify kernel source ;-) Basically, I added this patch to the kernel,
compiled it, enabled function tracing, and it crashed:
diff --git a/arch/x86/kernel/ftrace.c b/arch/x86/kernel/ftrace.c
index 8cabf63..9f354e5 100644
--- a/arch/x86/kernel/ftrace.c
+++ b/arch/x86/kernel/ftrace.c
@@ -586,6 +586,9 @@ void ftrace_replace_code(int enable)
for_ftrace_rec_iter(iter) {
rec = ftrace_rec_iter_record(iter);
+ if (count == 1000)
+ ret = -EPERM;
+ else
ret = add_breakpoints(rec, enable);
if (ret)
goto remove_breakpoints;
Not something that can be done from normal operations.
-- Steve
next prev parent reply other threads:[~2014-03-03 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 22:28 Steven Rostedt
[not found] ` <20140303224104.GA26031@kroah.com>
2014-03-03 22:45 ` Steven Rostedt [this message]
2014-03-03 22:49 ` Steven Rostedt
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=20140303174532.7cb8f31e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®