From: Hang Zhengyang via B4 Relay <devnull+hang.zhengyang1010.gmail.com@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Hang Zhengyang <hang.zhengyang1010@gmail.com>
Subject: [PATCH v2] perf parse-events: Don't report unreadable tracepoint globs as unknown
Date: Wed, 11 Nov 2026 09:48:50 +0800 [thread overview]
Message-ID: <20261111-tp-glob-errno-v2-1-ca45efb07d31@gmail.com> (raw)
From: Hang Zhengyang <hang.zhengyang1010@gmail.com>
As a normal user, a tracepoint glob gets the wrong error:
$ perf stat -e 'syscalls:*' true
event syntax error: 'syscalls:*'
\___ unknown tracepoint
Error: File /sys/kernel/tracing//events/syscalls/* not found.
Hint: Perhaps this kernel misses some CONFIG_ setting to enable this feature?.
add_tracepoint_multi_sys() returns ENOENT when nothing matched and
drops the error from reading the directories. Return that error
instead, so the glob reports what a plain tracepoint name does:
$ perf stat -e 'syscalls:*' true
event syntax error: 'syscalls:*'
\___ can't access trace events
Error: No permissions to read /sys/kernel/tracing//events/syscalls/*
Hint: Try 'sudo mount -o remount,mode=755 /sys/kernel/tracing/'
Fixes: d002aab87de8 ("perf tp_pmu: Factor existing tracepoint logic to new file")
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Hang Zhengyang <hang.zhengyang1010@gmail.com>
---
Thanks for the review, Ian.
---
Changes in v2:
- Show the output after the fix (Ian)
- Link to v1: https://lore.kernel.org/r/20261110-tp-glob-errno-v1-1-6c2cb609c590@gmail.com
---
tools/perf/util/parse-events.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
index f3ba70d4f76b..8a6d5a13863d 100644
--- a/tools/perf/util/parse-events.c
+++ b/tools/perf/util/parse-events.c
@@ -572,8 +572,10 @@ static int add_tracepoint_multi_sys(struct parse_events_state *parse_state,
ret = tp_pmu__for_each_tp_sys(&args, add_tracepoint_multi_sys_cb);
}
if (args.found == 0) {
- tracepoint_error(err, ENOENT, sys_glob, evt_glob, loc->first_column);
- return -ENOENT;
+ if (!ret)
+ ret = -ENOENT;
+ tracepoint_error(err, ret, sys_glob, evt_glob, loc->first_column);
+ return ret;
}
return ret;
}
---
base-commit: 13a8d580433a3b72b10be34f0e26787fe5659d3c
change-id: 20261110-tp-glob-errno-672ea1eb786b
Best regards,
--
Hang Zhengyang <hang.zhengyang1010@gmail.com>
reply other threads:[~2026-11-11 1:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261111-tp-glob-errno-v2-1-ca45efb07d31@gmail.com \
--to=devnull+hang.zhengyang1010.gmail.com@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=hang.zhengyang1010@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®