From: Andrew Morton <akpm@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Shreyas B Prabhu <shreyas@linux.vnet.ibm.com>,
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 13:36:01 -0700 [thread overview]
Message-ID: <20150512133601.2f619efe74d08ed9281667d1@linux-foundation.org> (raw)
In-Reply-To: <20150512160351.4b5d5606@gandalf.local.home>
On Tue, 12 May 2015 16:03:51 -0400 Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 12 May 2015 12:59:26 +0530
> Shreyas B Prabhu <shreyas@linux.vnet.ibm.com> wrote:
>
> > Hi Steven,
> > On closer look, there is no particular maintainer who picks changes to
> > this file. Can you please pick these up?
>
> Perhaps Andrew Morton?
>
> No problem, I can take these too.
>
I grabbed them, thanks.
> + TP_CONDITION(cpu_online(smp_processor_id())),
Are we sure these can't generate check_preemption_disabled() warnings?
Is there some reason why all these calls always occur with preemption
disabled?
next prev parent reply other threads:[~2015-05-12 20:36 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 ` [PATCH RESEND 0/3] tracing/mm: Fix suspicious rcu_dereference_check() usage warnings Shreyas B Prabhu
2015-05-12 20:03 ` Steven Rostedt
2015-05-12 20:36 ` Andrew Morton [this message]
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=20150512133601.2f619efe74d08ed9281667d1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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 \
--cc=shreyas@linux.vnet.ibm.com \
/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).