From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay.smtp-ext.broadcom.com (relay.smtp-ext.broadcom.com [192.19.144.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 07DBB386567; Tue, 29 Sep 2026 19:18:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.19.144.205 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790709524; cv=none; b=cvG/oql6SRgVXGh8oTIzkWbh4rsHU0XoI62kAky5h1wP5RwNrQJCwEhsrM2Iofe3igYQkz7MU38PhBXNCzThpZhf/rpI25GgJ7NOOdxYuRA0RueazvC2U9oU9LMfQMo9F+tEi27Ox9bFkwnoIgEfIelYFHhvSDoe4lTgdWB7i0k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790709524; c=relaxed/simple; bh=0xWh71AXUClW4+zVWoqRXMK4vlxF8HTlm1d/yKVFqtg=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=hKIGpHjRdTx5LhnNjH8Tqy7TRamedkZpX0f5p6PM4JTmy82Jqollu2ztFV3MpR3COKvGvDwOihLF21fuunjCPLQ4LjkKkSAAnS+zk6+PIW+6FR98T+NPIudG/dqN21OyGodghMuVDlbXyj7b6FLQ8JG2XjmYM3qK1iq/LKg6r9Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=broadcom.com; spf=fail smtp.mailfrom=broadcom.com; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b=PBoCJe9y; arc=none smtp.client-ip=192.19.144.205 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=broadcom.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=broadcom.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="PBoCJe9y" Received: from mail-acc-it-01.broadcom.com (mail-acc-it-01.acc.broadcom.net [10.35.36.83]) by relay.smtp-ext.broadcom.com (Postfix) with ESMTP id E8ADFC0003C7; Tue, 29 Sep 2026 12:18:41 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com E8ADFC0003C7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com; s=dkimrelay; t=1790709522; bh=0xWh71AXUClW4+zVWoqRXMK4vlxF8HTlm1d/yKVFqtg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=PBoCJe9yNd9cags1GN2BhFUWVj1avWxZVxpVCTLXLkTnfVVz/LFyMdvYofJtCjXvQ 2WKxNk3m+InpcceaEFpHwotQGA+iR2TwF1R97gfMuR1G5KnjQgj+Sy+0sNyW8r4ZOY mNozJIS1hGwFJYaYBJpwJRuhF5ySvMKQyVgQ5YHc= Received: from stbirv-lnx-1.igp.broadcom.net (stbirv-lnx-1.igp.broadcom.net [10.67.48.32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail-acc-it-01.broadcom.com (Postfix) with ESMTPSA id 56213AEA3; Tue, 29 Sep 2026 15:18:40 -0400 (EDT) From: Florian Fainelli To: stable@vger.kernel.org Cc: Namhyung Kim , Ian Rogers , Adrian Hunter , Ingo Molnar , Jiri Olsa , Kan Liang , Leo Yan , Peter Zijlstra , Arnaldo Carvalho de Melo , Florian Fainelli , Ingo Molnar , Arnaldo Carvalho de Melo , Mark Rutland , Alexander Shishkin , James Clark , Nick Terrell , David Sterba , Thomas Richter , linux-perf-users@vger.kernel.org (open list:PERFORMANCE EVENTS SUBSYSTEM), linux-kernel@vger.kernel.org (open list:PERFORMANCE EVENTS SUBSYSTEM), bpf@vger.kernel.org (open list:BPF [MISC]:Keyword:(?:\b|_)bpf(?:\b|_)) Subject: [PATCH stable 6.1 1/2] perf tools: Fix a asan issue in parse_events_multi_pmu_add() Date: Tue, 29 Sep 2026 12:18:33 -0700 Message-Id: <20260929191834.266354-2-florian.fainelli@broadcom.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20260929191834.266354-1-florian.fainelli@broadcom.com> References: <20260929191834.266354-1-florian.fainelli@broadcom.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Namhyung Kim commit 66c9598bd8916c6c1319d0100ac916cac89d4b0e upstream In the parse_events_multi_pmu_add() it passes the 'config' variable twice to parse_events_term__num() - one for config and another for loc_term. I'm not sure about the second one as it's converted to YYLTYPE variable. Asan reports it like below: In function ‘parse_events_term__num’, inlined from ‘parse_events_multi_pmu_add’ at util/parse-events.c:1602:6: util/parse-events.c:2653:64: error: array subscript ‘YYLTYPE[0]’ is partly outside array bounds of ‘char[8]’ [-Werror=array-bounds] 2653 | .err_term = loc_term ? loc_term->first_column : 0, | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~ util/parse-events.c: In function ‘parse_events_multi_pmu_add’: util/parse-events.c:1587:15: note: object ‘config’ of size 8 1587 | char *config; | ^~~~~~ cc1: all warnings being treated as errors Signed-off-by: Namhyung Kim Acked-by: Ian Rogers Cc: Adrian Hunter Cc: Ingo Molnar Cc: Jiri Olsa Cc: Kan Liang Cc: Leo Yan Cc: Peter Zijlstra Link: https://lore.kernel.org/r/20230331202949.810326-2-namhyung@kernel.org Signed-off-by: Arnaldo Carvalho de Melo Signed-off-by: Florian Fainelli --- tools/perf/util/parse-events.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c index 5973f46c2375..b77686a7bd26 100644 --- a/tools/perf/util/parse-events.c +++ b/tools/perf/util/parse-events.c @@ -1585,7 +1585,7 @@ int parse_events_multi_pmu_add(struct parse_events_state *parse_state, if (parse_events_term__num(&term, PARSE_EVENTS__TERM_TYPE_USER, - config, 1, false, &config, + config, 1, false, NULL, NULL) < 0) { free(config); goto out_err; -- 2.34.1