All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, ajax@redhat.com,
	gusld@br.ibm.com, a.p.zijlstra@chello.nl, paulus@samba.org,
	acme@ghostprotocols.net, torvalds@linux-foundation.org
Subject: Re: [GIT PULL events/urgent] Protect access via task_subsys_state_check()
Date: Thu, 25 Apr 2013 08:52:18 +0200	[thread overview]
Message-ID: <20130425065218.GB7806@gmail.com> (raw)
In-Reply-To: <20130424172912.GA31818@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> Hello, Ingo,
> 
> This pull request is for an RCU-related bug fix in perf_event_comm().
> Without this fix, RCU-lockdep splats and other failures result.
> 
> This fix is available in the git repository at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent
> 
> It has been subjected to -next testing and was posted to LKML at
> https://lkml.org/lkml/2013/4/19/403.
> 
> 							Thanx, Paul
> 
> ----------------------------------------------------------------
> Paul E. McKenney (1):
>       events: Protect access via task_subsys_state_check()
> 
>  kernel/events/core.c | 2 ++
>  1 file changed, 2 insertions(+)

So, I already have this as:

  c79aa0d96548 events: Protect access via task_subsys_state_check()

Given the urgency I applied it out of email and will send it to Linus 
later today.

Thanks,

	Ingo

  reply	other threads:[~2013-04-25  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 17:29 [GIT PULL events/urgent] Protect access via task_subsys_state_check() Paul E. McKenney
2013-04-25  6:52 ` Ingo Molnar [this message]
2013-04-25 13:23   ` Paul E. McKenney

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=20130425065218.GB7806@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=ajax@redhat.com \
    --cc=gusld@br.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=paulus@samba.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 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.