perf/core: Fix __perf_read_group_add() locking
authorPeter Zijlstra <peterz@infradead.org>
Tue, 5 Sep 2017 11:38:24 +0000 (13:38 +0200)
committerIngo Molnar <mingo@kernel.org>
Fri, 27 Oct 2017 08:31:57 +0000 (10:31 +0200)
Event timestamps are serialized using ctx->lock, make sure to hold it
over reading all values.

Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
kernel/events/core.c

index 5fae986..0f34f2a 100644 (file)
@@ -4453,6 +4453,8 @@ static int __perf_read_group_add(struct perf_event *leader,
        if (ret)
                return ret;
 
+       raw_spin_lock_irqsave(&ctx->lock, flags);
+
        /*
         * Since we co-schedule groups, {enabled,running} times of siblings
         * will be identical to those of the leader, so we only publish one
@@ -4475,8 +4477,6 @@ static int __perf_read_group_add(struct perf_event *leader,
        if (read_format & PERF_FORMAT_ID)
                values[n++] = primary_event_id(leader);
 
-       raw_spin_lock_irqsave(&ctx->lock, flags);
-
        list_for_each_entry(sub, &leader->sibling_list, group_entry) {
                values[n++] += perf_event_count(sub);
                if (read_format & PERF_FORMAT_ID)