From: eugene.loh@oracle.com
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH] test: Check for symbol ext4_dir_operations in module ext4
Date: Mon, 2 Mar 2026 16:51:12 -0500 [thread overview]
Message-ID: <20260302215112.4416-1-eugene.loh@oracle.com> (raw)
From: Eugene Loh <eugene.loh@oracle.com>
The tst.misc.d test assumes certain kernel symbols can be found. The
test specifies ext4`ext4_dir_operations, but there are apparently
kallmodsyms bugs that misassign the symbol to the wrong module.
Thus, the test fails to find the symbol. Meanwhile, we are less
concerned about such older kernel bugs, since we are moving from
kallmodsyms to modules.builtin.ranges.
Modify the .x file to check for ext4_dir_operations in the ext4 module
for those cases that rely on kallmodsyms.
Orabug: 37783183
Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
test/unittest/scalars/tst.misc.x | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/test/unittest/scalars/tst.misc.x b/test/unittest/scalars/tst.misc.x
index 1a1d9d271..ffef2fd33 100755
--- a/test/unittest/scalars/tst.misc.x
+++ b/test/unittest/scalars/tst.misc.x
@@ -1,11 +1,20 @@
#!/bin/sh
-if ! grep -qw isofs_dir_operations /proc/kallsyms; then
- exit 1
+if [ -e /proc/kallmodsyms ]; then
+ if ! grep -q 'isofs_dir_operations.*isofs' /proc/kallmodsyms; then
+ exit 1
+ fi
+
+ if ! grep -q 'ext4_dir_operations.*ext4' /proc/kallmodsyms; then
+ exit 1
+ fi
+ exit 0
fi
+if ! grep -qw isofs_dir_operations /proc/kallsyms; then
+ exit 1
+fi
if ! grep -qw ext4_dir_operations /proc/kallsyms; then
- exit 1
+ exit 1
fi
-
exit 0
--
2.47.3
next reply other threads:[~2026-03-02 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 21:51 eugene.loh [this message]
2026-03-03 14:52 ` [DTrace-devel] [PATCH] test: Check for symbol ext4_dir_operations in module ext4 Kris Van Hees
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=20260302215112.4416-1-eugene.loh@oracle.com \
--to=eugene.loh@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
/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