From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH v2 0/2] trace-cmd record: Fix compression on big-endian systems
Date: Sat, 12 Apr 2025 00:49:24 +0200 [thread overview]
Message-ID: <20250411225648.6498-1-iii@linux.ibm.com> (raw)
v1: https://lore.kernel.org/linux-trace-devel/20250411172815.61477-1-iii@linux.ibm.com/
v1 -> v2: Factor out read_size_val(), split out the error handling
change (Steven).
Hi,
While running trace-cmd on s390x, I ran into a few issues.
This is the fix for the first one: trace-cmd report prints nothing.
The second one is a kernel issue [1], which causes trace-cmd to print
a lot of bogus space characters.
The final one is "error in size of file '/proc/kallsyms'" caused by
delayed removal of a BPF program from /proc/kallsyms. I plan to fix it
by reading the contents of /proc/kallsyms into a temporary file before
writing it into the trace file.
[1] https://lore.kernel.org/lkml/20250411172207.61332-1-iii@linux.ibm.com/
Best regards,
Ilya
Ilya Leoshkevich (2):
trace-cmd record: Fix compression on big-endian systems
libtracecmd: Add missing error handling to trace-compress.c
lib/trace-cmd/trace-compress.c | 32 +++++++++++++++++++++++++-------
1 file changed, 25 insertions(+), 7 deletions(-)
--
2.49.0
next reply other threads:[~2025-04-11 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 22:49 Ilya Leoshkevich [this message]
2025-04-11 22:49 ` [PATCH v2 1/2] trace-cmd record: Fix compression on big-endian systems Ilya Leoshkevich
2025-04-11 22:49 ` [PATCH v2 2/2] libtracecmd: Add missing error handling to trace-compress.c Ilya Leoshkevich
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=20250411225648.6498-1-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).