From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [GIT PULL] perf crash fix
Date: Thu, 03 Jun 2010 11:26:42 +0200 [thread overview]
Message-ID: <1275557202.27810.35201.camel@twins> (raw)
In-Reply-To: <1275534810-1837-1-git-send-regression-fweisbec@gmail.com>
On Thu, 2010-06-03 at 05:13 +0200, Frederic Weisbecker wrote:
> What happens here is a double pmu->disable() due to a race between
> two perf_adjust_period().
>
> We first overflow a page fault event and then re-adjust the period.
> When we reset the period_left, we stop the pmu by removing the
> perf event from the software event hlist. And just before we
> re-enable it, we are interrupted by a sched tick that also tries to
> re-adjust the period. There we eventually disable the event a second
> time, which leads to a double hlist_del_rcu() that ends up
> dereferencing LIST_POISON2.
>
> In fact, the goal of embracing the reset of the period_left with
> a pmu:stop() and pmu:start() is only relevant to hardware events. We
> want them to reprogram the next period interrupt.
>
> But this is useless for software events. They have their own way to
> handle the period left, and in a non-racy way. They don't need to
> be stopped here.
>
> So, use a new pair of perf_event_stop/start_hwevent that only stop
> and restart hardware events in this path.
>
> The race won't happen with hardware events as sched ticks can't
> happen during nmis.
I've queued the below.
---
Subject: perf: Fix crash in swevents
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date: Thu Jun 03 11:21:20 CEST 2010
Frederic reported that because swevents handling doesn't disable IRQs
anymore, we can get a recursion of perf_adjust_period(), once from
overflow handling and once from the tick.
If both call ->disable, we get a double hlist_del_rcu() and trigger
a LIST_POISON2 dereference.
Since we don't actually need to stop/start a swevent to re-programm
the hardware (lack of hardware to program), simply nop out these
callbacks for the swevent pmu.
Reported-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
kernel/perf_event.c | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
Index: linux-2.6/kernel/perf_event.c
===================================================================
--- linux-2.6.orig/kernel/perf_event.c
+++ linux-2.6/kernel/perf_event.c
@@ -4055,13 +4055,6 @@ static void perf_swevent_overflow(struct
}
}
-static void perf_swevent_unthrottle(struct perf_event *event)
-{
- /*
- * Nothing to do, we already reset hwc->interrupts.
- */
-}
-
static void perf_swevent_add(struct perf_event *event, u64 nr,
int nmi, struct perf_sample_data *data,
struct pt_regs *regs)
@@ -4276,11 +4269,17 @@ static void perf_swevent_disable(struct
hlist_del_rcu(&event->hlist_entry);
}
+static void perf_swevent_nop(struct perf_event *event)
+{
+}
+
static const struct pmu perf_ops_generic = {
.enable = perf_swevent_enable,
.disable = perf_swevent_disable,
+ .start = perf_swevent_nop,
+ .stop = perf_swevent_nop,
.read = perf_swevent_read,
- .unthrottle = perf_swevent_unthrottle,
+ .unthrottle = perf_swevent_nop, /* hwc->interrupts already reset */
};
/*
next prev parent reply other threads:[~2010-06-03 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 3:13 [GIT PULL] perf crash fix Frederic Weisbecker
2010-06-03 8:02 ` Peter Zijlstra
2010-06-03 9:08 ` Peter Zijlstra
2010-06-03 12:35 ` Frederic Weisbecker
2010-06-03 12:40 ` Peter Zijlstra
2010-06-03 12:42 ` Frederic Weisbecker
2010-06-03 9:26 ` Peter Zijlstra [this message]
2010-06-03 9:33 ` Peter Zijlstra
2010-06-03 17:54 ` [tip:perf/urgent] perf: Fix crash in swevents 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=1275557202.27810.35201.camel@twins \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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