From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] [RFC] perf: Fix a race between ring_buffer_detach() and ring_buffer_wakeup()
Date: Wed, 7 May 2014 20:06:21 +0200 [thread overview]
Message-ID: <20140507180621.GE13658@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140507123526.GD13658@twins.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
On Wed, May 07, 2014 at 02:35:26PM +0200, Peter Zijlstra wrote:
> static void ring_buffer_attach(struct perf_event *event,
> struct ring_buffer *rb)
> {
> + struct ring_buffer *old_rb = NULL;
> unsigned long flags;
>
> + if (event->rb) {
> + /*
> + * Should be impossible, we set this when removing
> + * event->rb_entry and wait/clear when adding event->rb_entry.
> + */
> + WARN_ON_ONCE(event->rcu_pending);
>
> + old_rb = event->rb;
> + event->rcu_batches = get_state_synchronize_rcu();
> + event->rcu_pending = 1;
>
> + spin_lock_irqsave(&rb->event_lock, flags);
> + list_del_rcu(&event->rb_entry);
> + spin_unlock_irqrestore(&rb->event_lock, flags);
This all works a whole lot better if you make that old_rb->event_lock.
> + }
>
> + if (event->rcu_pending && rb) {
> + cond_synchronize_rcu(event->rcu_batches);
> + event->rcu_pending = 0;
> + }
>
> + if (rb) {
> + spin_lock_irqsave(&rb->event_lock, flags);
> + list_add_rcu(&event->rb_entry, &rb->event_list);
> + spin_unlock_irqrestore(&rb->event_lock, flags);
> + }
> +
> + rcu_assign_pointer(event->rb, rb);
> +
> + if (old_rb) {
> + ring_buffer_put(old_rb);
> + /*
> + * Since we detached before setting the new rb, so that we
> + * could attach the new rb, we could have missed a wakeup.
> + * Provide it now.
> + */
> + wake_up_all(&event->waitq);
> + }
> }
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-07 18:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 13:38 [PATCH] [RFC] perf: Fix a race between ring_buffer_detach() and ring_buffer_wakeup() Alexander Shishkin
2014-03-13 19:58 ` Paul E. McKenney
2014-03-14 9:50 ` Peter Zijlstra
2014-03-14 20:47 ` Paul E. McKenney
2014-03-14 22:43 ` Peter Zijlstra
2014-03-14 23:02 ` Paul E. McKenney
2014-03-15 0:00 ` Paul E. McKenney
2014-03-17 11:18 ` Peter Zijlstra
2014-03-17 16:48 ` Paul E. McKenney
2014-03-17 17:30 ` Peter Zijlstra
2014-03-18 2:45 ` Paul E. McKenney
2014-03-18 8:26 ` Peter Zijlstra
2014-05-07 12:35 ` Peter Zijlstra
2014-05-07 18:06 ` Peter Zijlstra [this message]
2014-05-08 15:37 ` Paul E. McKenney
2014-05-08 16:09 ` Peter Zijlstra
2014-05-19 12:48 ` [tip:perf/urgent] perf: Fix a race between ring_buffer_detach() and ring_buffer_attach() tip-bot for 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=20140507180621.GE13658@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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