From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753363AbcHJUOf (ORCPT ); Wed, 10 Aug 2016 16:14:35 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:32814 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934099AbcHJUO1 (ORCPT ); Wed, 10 Aug 2016 16:14:27 -0400 Date: Wed, 10 Aug 2016 13:04:38 +0200 From: Ingo Molnar To: David Carrillo-Cisneros Cc: linux-kernel@vger.kernel.org, "x86@kernel.org" , Ingo Molnar , Thomas Gleixner , Andi Kleen , Kan Liang , Peter Zijlstra , Vegard Nossum , Paul Turner , Stephane Eranian Subject: Re: [PATCH v2 1/4] perf/core: check return value of perf_event_read IPI Message-ID: <20160810110437.GB14283@gmail.com> References: <1470539577-102094-1-git-send-email-davidcc@google.com> <1470539577-102094-2-git-send-email-davidcc@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1470539577-102094-2-git-send-email-davidcc@google.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * David Carrillo-Cisneros wrote: > The call to smp_call_function_single in perf_event_read() may fail and, > when it does, its error value is the one to return. > > Signed-off-by: David Carrillo-Cisneros > Reviewed-by: Stephane Eranian > --- > kernel/events/core.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/kernel/events/core.c b/kernel/events/core.c > index 9345028..96523fd 100644 > --- a/kernel/events/core.c > +++ b/kernel/events/core.c > @@ -3469,9 +3469,9 @@ static int perf_event_read(struct perf_event *event, bool group) > .group = group, > .ret = 0, > }; > - smp_call_function_single(event->oncpu, > - __perf_event_read, &data, 1); > - ret = data.ret; > + ret = smp_call_function_single(event->oncpu, > + __perf_event_read, &data, 1); > + ret = ret ? : data.ret; > } else if (event->state == PERF_EVENT_STATE_INACTIVE) { > struct perf_event_context *ctx = event->ctx; > unsigned long flags; Please also describe the symptoms of the bug - under what circumstances may the smp-call fail and how does the user notice? Thanks, Ingo