From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
a.p.zijlstra@chello.nl, paulus@samba.org, acme@redhat.com
Subject: Re: [PATCH RFC] perf: fix find_swevent_head() RCU lockdep splat
Date: Thu, 13 May 2010 21:03:28 +0200 [thread overview]
Message-ID: <20100513190325.GB5377@nowhere> (raw)
In-Reply-To: <20100513182556.GA14326@linux.vnet.ibm.com>
On Thu, May 13, 2010 at 11:25:56AM -0700, Paul E. McKenney wrote:
> This commit guesses at the perf_cpu_context locking design and deploys
> an rcu_dereference_check() accordingly. The design appears to require
> that a given CPU be accessing its own per_cpu_context or that it be
> traversing under RCU protection.
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
>
> perf_event.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/perf_event.c b/kernel/perf_event.c
> index a4fa381..002791c 100644
> --- a/kernel/perf_event.c
> +++ b/kernel/perf_event.c
> @@ -4074,7 +4074,9 @@ find_swevent_head(struct perf_cpu_context *ctx, u64 type, u32 event_id)
>
> hash = swevent_hash(type, event_id);
>
> - hlist = rcu_dereference(ctx->swevent_hlist);
> + hlist = rcu_dereference_check(ctx->swevent_hlist,
> + rcu_read_lock_held() ||
> + ctx == &__get_cpu_var(perf_cpu_context));
> if (!hlist)
> return NULL;
>
Hmm, that's not exactly that. It will always be the ctx of this cpu
but not always under rcu read lock. I mean touching the current cpu
ctx is not inherently safe.
In fact we have two paths:
perf_swevent_enable() gets the hlist and if it is called it means
that this hlist is not supposed to be NULL. If it is, it's a bug.
If we have created a software event, the hlist has been allocated
and perf_swevent_enable() is called later to activate this event.
May be I shouldn't use rcu_dereference() here but a simple dereference.
And the hlist can't be freed under us at this time so we don't need
rcu_read_lock().
OTOH, do_perf_sw_event() can be called anytime so it need this
rcu_read_lock().
On the perf_swevent_enable() path, what prevents the hlist to be
freed under us is the ctx->lock. Because we won't ever remove
an event from its context list outside this lock, and we might only
release the hlist after a software event gets removed from its
context list.
So either we do this:
hlist = rcu_dereference_check(ctx->swevent_hlist,
rcu_read_lock_held() ||
raw_spin_lock_is_held(&ctx->lock));
or:
hlist = ctx->swevent_hlist;
next prev parent reply other threads:[~2010-05-13 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 18:25 [PATCH RFC] perf: fix find_swevent_head() RCU lockdep splat Paul E. McKenney
2010-05-13 19:03 ` Frederic Weisbecker [this message]
2010-05-13 19:46 ` Paul E. McKenney
2010-05-13 20:26 ` Frederic Weisbecker
2010-05-13 20:48 ` Frederic Weisbecker
2010-05-13 20:59 ` Frederic Weisbecker
2010-05-13 23:43 ` Paul E. McKenney
2010-05-20 7:01 ` Frederic Weisbecker
2010-05-14 7:47 ` Peter Zijlstra
2010-05-20 7:04 ` Frederic Weisbecker
2010-05-14 7:44 ` Peter Zijlstra
2010-05-20 7:04 ` Frederic Weisbecker
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=20100513190325.GB5377@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.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