From: Wei Gao via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] nm01: Fix BSD vs POSIX format comparison failure on Power
Date: Wed, 13 May 2026 08:51:13 +0000 [thread overview]
Message-ID: <20260513085124.12324-1-wegao@suse.com> (raw)
In-Reply-To: <20260513021036.12127-1-wegao@suse.com>
On Power architecture, symbol names can contain hex-like prefixes such
as "0000003e.plt_call.__gmon_start__".
In our openqa specific power system, the gensub seems has some
compatible issue which you can see following trace, the BSD format's
symbol name was incorrectly trimmed to ".plt_call.__gmon_start__"
(losing the "3e"), while the POSIX format kept it as
"3e.plt_call.__gmon_start__".
Example failure from a Power machine:
--- DEBUG nm01_sh ---
--- RAW BSD ---
00000000000005e0 t 0000003e.plt_call.__gmon_start__
--- RAW POSIX ---
0000003e.plt_call.__gmon_start__ t 5e0
--- REPRO LTP LOGIC ---
--- TRIMMED BSD ---
5e0 t .plt_call.__gmon_start__
--- TRIMMED POSIX ---
3e.plt_call.__gmon_start__ t 5e0
--- REORDERED BSD (nm1) ---
.plt_call.__gmon_start__t5e0
--- REORDERED POSIX (nm2) ---
3e.plt_call.__gmon_start__t5e0
--- DIFF RESULT ---
--- /tmp/dbg_nm1 2026-05-11 22:33:54.754648941 -0400
+++ /tmp/dbg_nm2 2026-05-11 22:33:54.761924742 -0400
@@ -1,7 +1,7 @@
-.plt_call.__gmon_start__t5e0
+3e.plt_call.__gmon_start__t5e0
--- END DEBUG ---
Replace the global gensub to simple sub approach with targeted field processing in awk
can fix the issue.
Signed-off-by: Wei Gao <wegao@suse.com>
---
v1->v2:
Update commit message to fix patch apply error
testcases/commands/nm/nm01.sh | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)
diff --git a/testcases/commands/nm/nm01.sh b/testcases/commands/nm/nm01.sh
index c795d47ff..2ca73c4ea 100755
--- a/testcases/commands/nm/nm01.sh
+++ b/testcases/commands/nm/nm01.sh
@@ -83,17 +83,28 @@ test5()
EXPECT_PASS $NM -f bsd $TST_DATAROOT/f1 \> nm_bsd.out
EXPECT_PASS $NM -f posix $TST_DATAROOT/f1 \> nm_posix.out
- ROD awk '{print gensub(/\y(0+)([0-9a-fA-F]+)\y/, "\\2", "g")}' nm_bsd.out \> trimmed_nm_bsd.out
- ROD awk '{print gensub(/\y(0+)([0-9a-fA-F]+)\y/, "\\2", "g")}' nm_posix.out \> trimmed_nm_posix.out
-
- ROD awk '{print $3 $2 $1}' trimmed_nm_bsd.out \> nm1.out
- ROD awk '{print $1 $2 $3}' trimmed_nm_posix.out \> nm2.out
+ ROD awk '{
+ if (NF == 2) { val = "0"; type = $1; name = $2; }
+ else { val = $1; type = $2; name = $3; }
+ sub(/^0+/, "", val); if (val == "") val = "0";
+ sub(/^0+/, "", name);
+ print name type val
+ }' nm_bsd.out \> nm1.out
+
+ ROD awk '{
+ val = $3; type = $2; name = $1;
+ sub(/^0+/, "", val); if (val == "") val = "0";
+ sub(/^0+/, "", name);
+ print name type val
+ }' nm_posix.out \> nm2.out
if diff nm1.out nm2.out > /dev/null; then
tst_res TPASS "Got BSD format with -f bsd"
else
tst_res TFAIL "Got wrong format with -f bsd"
cat nm_bsd.out
+ cat nm_posix.out
+ diff -u nm1.out nm2.out
fi
}
--
2.52.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-13 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 2:10 [LTP] [PATCH v1] nm01: Fix BSD vs POSIX format comparison failure on Power Wei Gao via ltp
2026-05-13 7:59 ` Andrea Cervesato via ltp
2026-05-13 8:51 ` Wei Gao via ltp [this message]
2026-05-13 10:37 ` [LTP] " linuxtestproject.agent
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=20260513085124.12324-1-wegao@suse.com \
--to=ltp@lists.linux.it \
--cc=wegao@suse.com \
/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