[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-724b6daa13e100067c30cfc4d1ad06629609dc4e@git.kernel.org>
Date: Thu, 26 Apr 2012 05:16:23 -0700
From: tip-bot for Michael Ellerman <michael@...erman.id.au>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
a.p.zijlstra@...llo.nl, michael@...erman.id.au, tglx@...utronix.de
Subject: [tip:perf/urgent] perf: Fix perf_event_for_each() to use sibling
Commit-ID: 724b6daa13e100067c30cfc4d1ad06629609dc4e
Gitweb: http://git.kernel.org/tip/724b6daa13e100067c30cfc4d1ad06629609dc4e
Author: Michael Ellerman <michael@...erman.id.au>
AuthorDate: Wed, 11 Apr 2012 11:54:13 +1000
Committer: Ingo Molnar <mingo@...nel.org>
CommitDate: Thu, 26 Apr 2012 13:51:31 +0200
perf: Fix perf_event_for_each() to use sibling
In perf_event_for_each() we call a function on an event, and then
iterate over the siblings of the event.
However we don't call the function on the siblings, we call it
repeatedly on the original event - it seems "obvious" that we should
be calling it with sibling as the argument.
It looks like this broke in commit 75f937f24bd9 ("Fix ctx->mutex
vs counter->mutex inversion").
The only effect of the bug is that the PERF_IOC_FLAG_GROUP parameter
to the ioctls doesn't work.
Signed-off-by: Michael Ellerman <michael@...erman.id.au>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Link: http://lkml.kernel.org/r/1334109253-31329-1-git-send-email-michael@ellerman.id.au
Signed-off-by: Ingo Molnar <mingo@...nel.org>
---
kernel/events/core.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index a6a9ec4..fd126f8 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -3183,7 +3183,7 @@ static void perf_event_for_each(struct perf_event *event,
perf_event_for_each_child(event, func);
func(event);
list_for_each_entry(sibling, &event->sibling_list, group_entry)
- perf_event_for_each_child(event, func);
+ perf_event_for_each_child(sibling, func);
mutex_unlock(&ctx->mutex);
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists