stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH][GIT PULL][3.9] tracing: Fix free of probe entry by calling call_rcu_sched()
Date: Thu, 14 Mar 2013 08:13:09 +0100	[thread overview]
Message-ID: <20130314071309.GA7869@gmail.com> (raw)
In-Reply-To: <1363218811.25967.12.camel@gandalf.local.home>


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

> Ingo,
> 
> While testing my new code I stumbled upon this bug. This is a real
> bug and has been in the kernel forever. Luckily, it's in a feature
> that is seldom used. But it can cause a crash if the race is hit.
> 
> I based this off of my last pull request of tip/perf/urgent.
> 
> Thanks,
> 
> -- Steve
> 
> 
> Please pull the latest tip/perf/urgent-2 tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> tip/perf/urgent-2
> 
> Head SHA1: 740466bc89ad8bd5afcc8de220f715f62b21e365
> 
> 
> Steven Rostedt (Red Hat) (1):
>       tracing: Fix free of probe entry by calling call_rcu_sched()
> 
> ----
>  kernel/trace/ftrace.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Pulled, thanks Steve!

	Ingo

      reply	other threads:[~2013-03-14  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 23:53 [PATCH][GIT PULL][3.9] tracing: Fix free of probe entry by calling call_rcu_sched() Steven Rostedt
2013-03-14  7:13 ` 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=20130314071309.GA7869@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).