linux-kernel - [PATCH v1 14/17] perf tests kallsyms: Add basic kallsyms test

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251122081929.7588-15-irogers@google.com>
Date: Sat, 22 Nov 2025 00:19:26 -0800
From: Ian Rogers <irogers@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, 
	Arnaldo Carvalho de Melo <acme@...nel.org>, Namhyung Kim <namhyung@...nel.org>, 
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>, 
	Ian Rogers <irogers@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>, 
	James Clark <james.clark@...aro.org>, Collin Funk <collin.funk1@...il.com>, 
	Dmitry Vyukov <dvyukov@...gle.com>, Andi Kleen <ak@...ux.intel.com>, 
	Thomas Falcon <thomas.falcon@...el.com>, Leo Yan <leo.yan@....com>, 
	Yicong Yang <yangyicong@...ilicon.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
	"Masami Hiramatsu (Google)" <mhiramat@...nel.org>, Stephen Brennan <stephen.s.brennan@...cle.com>, 
	Haibo Xu <haibo1.xu@...el.com>, linux-kernel@...r.kernel.org, 
	linux-perf-users@...r.kernel.org
Subject: [PATCH v1 14/17] perf tests kallsyms: Add basic kallsyms test

Add test that kallsyms finds a well known symbol and fails for
another.

Signed-off-by: Ian Rogers <irogers@...gle.com>
---
 tools/perf/tests/shell/kallsyms.sh | 56 ++++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100755 tools/perf/tests/shell/kallsyms.sh

diff --git a/tools/perf/tests/shell/kallsyms.sh b/tools/perf/tests/shell/kallsyms.sh
new file mode 100755
index 000000000000..d0eb99753f47
--- /dev/null
+++ b/tools/perf/tests/shell/kallsyms.sh
@@ -0,0 +1,56 @@
+#!/bin/bash
+# perf kallsyms tests
+# SPDX-License-Identifier: GPL-2.0
+
+err=0
+
+test_kallsyms() {
+	echo "Basic perf kallsyms test"
+
+	# Check if /proc/kallsyms is readable
+	if [ ! -r /proc/kallsyms ]; then
+		echo "Basic perf kallsyms test [Skipped: /proc/kallsyms not readable]"
+		err=2
+		return
+	fi
+
+	# Use a symbol that is definitely a function and present in all kernels, e.g. schedule
+	symbol="schedule"
+
+	# Run perf kallsyms
+	# It prints "address symbol_name"
+	output=$(perf kallsyms $symbol 2>&1)
+	ret=$?
+
+	if [ $ret -ne 0 ] || [ -z "$output" ]; then
+		# If empty or failed, it might be due to permissions (kptr_restrict)
+		# Check if we can grep the symbol from /proc/kallsyms directly
+		if grep -q "$symbol" /proc/kallsyms 2>/dev/null; then
+			# If it's in /proc/kallsyms but perf kallsyms returned empty/error,
+			# it likely means perf couldn't parse it or access it correctly (e.g. kptr_restrict=2).
+			echo "Basic perf kallsyms test [Skipped: $symbol found in /proc/kallsyms but perf kallsyms failed (output: '$output')]"
+			err=2
+			return
+		else
+			echo "Basic perf kallsyms test [Skipped: $symbol not found in /proc/kallsyms]"
+			err=2
+			return
+		fi
+	fi
+
+	if echo "$output" | grep -q "not found"; then
+		echo "Basic perf kallsyms test [Failed: output '$output' does not contain $symbol]"
+		err=1
+		return
+	fi
+
+	if perf kallsyms ErlingHaaland | grep -vq "not found"; then
+		echo "Basic perf kallsyms test [Failed: ErlingHaaland found in the output]"
+		err=1
+		return
+	fi
+	echo "Basic perf kallsyms test [Success]"
+}
+
+test_kallsyms
+exit $err
-- 
2.52.0.rc2.455.g230fcf2819-goog