From: eugene.loh@oracle.com
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: [PATCH 1/2] test: Allow more variations in expected fbt kernel stacks
Date: Sat, 8 Feb 2025 18:21:05 -0500 [thread overview]
Message-ID: <20250208232106.27146-1-eugene.loh@oracle.com> (raw)
From: Eugene Loh <eugene.loh@oracle.com>
This test checks the call stack upon entry to vfs_write().
Unfortunately, these checks require some maintenance since the call
stack can vary -- slightly or greatly -- depending on processor or
kernel. There is a competition between ease of test maintenance and
strictness of correctness checks.
Adapt post processing of output to allow new variations in stacks
seen in UEK 8 (currently Linux 6.12).
Orabug: 37459289
Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
---
test/unittest/stack/tst.stack_fbt.sh | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/test/unittest/stack/tst.stack_fbt.sh b/test/unittest/stack/tst.stack_fbt.sh
index c365e14d6..8a0b7999c 100755
--- a/test/unittest/stack/tst.stack_fbt.sh
+++ b/test/unittest/stack/tst.stack_fbt.sh
@@ -37,9 +37,18 @@ if [ $? -ne 0 ]; then
exit 1
fi
-# Strip out blank lines and pointer values.
-
-awk 'NF != 0 { sub(/+0x[0-9a-f]*$/, "+{ptr}"); print }' dtrace.out > dtrace.post
+# Strip out
+# - blank lines
+# - "constprop"
+# - "isra"
+# - "_after_hwframe" (x86 starting with UEK8)
+# - pointer values
+
+awk 'NF != 0 { sub("\\.constprop\\.[0-9]", "");
+ sub("\\.isra\\.[0-9]", "");
+ sub("_after_hwframe\\+", "+");
+ sub(/+0x[0-9a-f]*$/, "+{ptr}");
+ print }' dtrace.out > dtrace.post
if [ $? -ne 0 ]; then
echo ERROR: awk failed
cat dtrace.out
--
2.43.5
next reply other threads:[~2025-02-08 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 23:21 eugene.loh [this message]
2025-02-08 23:21 ` [PATCH 2/2] test: Account for pid:::entry ustack() being correct eugene.loh
2025-02-28 16:00 ` Kris Van Hees
2025-02-28 15:47 ` [PATCH 1/2] test: Allow more variations in expected fbt kernel stacks 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=20250208232106.27146-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.