mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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:49:34 -0500	[thread overview]
Message-ID: <20140303174934.7e5971d8@gandalf.local.home> (raw)
In-Reply-To: <20140303174532.7cb8f31e@gandalf.local.home>

On Mon, 3 Mar 2014 17:45:32 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:


> 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.
> 

I'll also add that one reason that this hasn't been an issue before, is
that the code that converts calls to mcount to nops, is done at kernel
boot up. If the above code were to fail, it is highly likely that the
code that converted mcount to nops would fail too. And if that happens,
it completely disables function tracing, preventing this code from
running.

The code that converts mcount to nops, handles the above error properly.

-- Steve

      reply	other threads:[~2014-03-03 22:49 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
2014-03-03 22:49     ` 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=20140303174934.7e5971d8@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®