All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH 0/2] tracing/urgent: fixes for nop patching omissions
Date: Sat, 20 Jun 2009 07:06:10 +0200	[thread overview]
Message-ID: <1245474372-5249-1-git-send-email-fweisbec@gmail.com> (raw)

Hi Ingo, Steven,

The first patch in the set fixes a bug on which ftrace silently
ommitted to recover nop patching after function tracing.

The issue is present in .31 and .30 as well

The second patch just adds a warning to prevent further mistakes like
that.

Thanks.

Frederic Weisbecker (2):
  tracing/urgent: fix unbalanced ftrace_start_up
  tracing/urgent: warn in case of ftrace_start_up inbalance

 kernel/trace/ftrace.c          |    7 +++++++
 kernel/trace/trace_functions.c |    8 +++++---
 2 files changed, 12 insertions(+), 3 deletions(-)

The following changes since commit 44ad18e0a65e296b2e68a1452509f6222cdce743:
  Steven Rostedt (1):
        tracing: update sample event documentation

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	tracing/urgent

Frederic Weisbecker (2):
      tracing/urgent: fix unbalanced ftrace_start_up
      tracing/urgent: warn in case of ftrace_start_up inbalance

 kernel/trace/ftrace.c          |    7 +++++++
 kernel/trace/trace_functions.c |    8 +++++---
 2 files changed, 12 insertions(+), 3 deletions(-)

             reply	other threads:[~2009-06-20  5:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20  5:06 Frederic Weisbecker [this message]
2009-06-20  5:06 ` [PATCH 1/2] tracing/urgent: fix unbalanced ftrace_start_up Frederic Weisbecker
2009-06-20  5:06 ` [PATCH 2/2] tracing/urgent: warn in case of ftrace_start_up inbalance Frederic Weisbecker
2009-06-20 15:11 ` [PATCH 0/2] tracing/urgent: fixes for nop patching omissions Ingo Molnar

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=1245474372-5249-1-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.