From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"ak@linux.intel.com" <ak@linux.intel.com>,
Eric Dumazet <edumazet@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf/core: fix RCU issues with cgroup monitoring mode
Date: Mon, 19 Oct 2015 11:12:25 +0200 [thread overview]
Message-ID: <20151019091225.GH3816@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CABPqkBS88_p7DZwVPKgEz0HSqth5zzhFjpRzeF8O9HhYByEJmg@mail.gmail.com>
On Mon, Oct 19, 2015 at 12:58:47AM -0700, Stephane Eranian wrote:
> Peter,
>
> On Sat, Oct 17, 2015 at 2:56 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Sat, Oct 17, 2015 at 03:28:11AM +0200, Stephane Eranian wrote:
> > >
> > > This patch eliminates all known RCU violations detected
> > > by the RCU checker (PROVE_RCU). The impact code paths
> > > were all related to cgroup mode monitoring and involved
> > > access a task's cgrp.
> >
> > But were they right? This patch provides no clues.
> >
> I am assuming that is the checker detects something suspicious there is likely
> a problem.
>
> Take for instance:
> perf_cgroup_sched_out()->perf_cgroup_from_task() ->task_subsys_state()
>
> That one fires the checker. I think because we are accessing the css
> state without
> protection.
>
> The other places are similar.
But perf_cgroup_attach()->perf_cgroup_switch() takes ctx->lock().
Therefore; if you hold ctx->lock, the cgroup is pinned.
And the above sequence very much holds ctx->lock.
Right?
So it looks to me that we should teach perf_cgroup_from_task() about
ctx->lock or something.
next prev parent reply other threads:[~2015-10-19 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 1:28 Stephane Eranian
2015-10-17 9:56 ` Peter Zijlstra
2015-10-19 7:58 ` Stephane Eranian
2015-10-19 9:12 ` Peter Zijlstra [this message]
2015-10-26 19:27 ` Stephane Eranian
2015-10-26 20:20 ` Peter Zijlstra
2015-10-17 10:00 ` Peter Zijlstra
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=20151019091225.GH3816@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=edumazet@google.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome