public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shreyas B Prabhu <shreyas@linux.vnet.ibm.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
	aneesh.kumar@linux.vnet.ibm.com, paulmck@linux.vnet.ibm.com,
	preeti@linux.vnet.ibm.com, mgorman@suse.de, namhyung@kernel.org,
	lizf@cn.fujitsu.com, acme@redhat.com
Subject: Re: [PATCH RESEND 0/3] tracing/mm: Fix suspicious rcu_dereference_check() usage warnings
Date: Tue, 12 May 2015 12:59:26 +0530	[thread overview]
Message-ID: <5551ABD6.9050007@linux.vnet.ibm.com> (raw)
In-Reply-To: <1431105646-26558-1-git-send-email-shreyas@linux.vnet.ibm.com>

Hi Steven,
On closer look, there is no particular maintainer who picks changes to
this file. Can you please pick these up?

On Friday 08 May 2015 10:50 PM, Shreyas B. Prabhu wrote:
> Since tracepoints use RCU for protection, they must not be called on
> offline cpus. Running with LOCKDEP enabled discovered few scenarios
> where trace points were called on offline cpus. These patches fix
> this by converting these trace events into conditonal trace events
> where condition is cpu_online(smp_processor_id())
> 
> Previous posting of the patchset can be found here:
> https://lkml.org/lkml/2015/4/28/512
> 
> This resend CCs people who added/edited the trace events in question.
> 
> Shreyas B. Prabhu (3):
>   tracing/mm: Don't trace kmem_cache_free on offline cpus
>   tracing/mm: Don't trace mm_page_free on offline cpus
>   tracing/mm: Don't trace mm_page_pcpu_drain on offline cpus
> 
>  include/trace/events/kmem.h | 26 ++++++++++++++++++++++----
>  1 file changed, 22 insertions(+), 4 deletions(-)
> 


  parent reply	other threads:[~2015-05-12  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 17:20 [PATCH RESEND 0/3] tracing/mm: Fix suspicious rcu_dereference_check() usage warnings Shreyas B. Prabhu
2015-05-08 17:20 ` [PATCH RESEND 1/3] tracing/mm: Don't trace kmem_cache_free on offline cpus Shreyas B. Prabhu
2015-05-08 17:20 ` [PATCH RESEND 2/3] tracing/mm: Don't trace mm_page_free " Shreyas B. Prabhu
2015-05-08 17:20 ` [PATCH RESEND 3/3] tracing/mm: Don't trace mm_page_pcpu_drain " Shreyas B. Prabhu
2015-05-12  7:29 ` Shreyas B Prabhu [this message]
2015-05-12 20:03   ` [PATCH RESEND 0/3] tracing/mm: Fix suspicious rcu_dereference_check() usage warnings Steven Rostedt
2015-05-12 20:36     ` Andrew Morton
2015-05-12 20:54       ` Steven Rostedt
2015-05-13  7:47         ` Shreyas B Prabhu
2015-05-14 20:08           ` Andrew Morton
2015-05-14 20:38             ` 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=5551ABD6.9050007@linux.vnet.ibm.com \
    --to=shreyas@linux.vnet.ibm.com \
    --cc=acme@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=preeti@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox