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 v3 0/2] libtracecmd: Support changing /proc/kallsyms
Date: Fri, 11 Jul 2025 15:25:34 +0200 [thread overview]
Message-ID: <20250711132802.1781-1-iii@linux.ibm.com> (raw)
v2: https://lore.kernel.org/linux-trace-devel/20250602214154.446881-1-iii@linux.ibm.com/
v2 -> v3: Add a comment and some newlines (Steven).
v1: https://lore.kernel.org/linux-trace-devel/20250416231325.14113-1-iii@linux.ibm.com/
v1 -> v2: Rewrite the size instead of reading the file twice (Steven).
Turns out exposing do_lseek() is not necessary, since
everything is in the same C file.
Hi,
this series fixes tracing in presence of frequent BPF or kernel module
loads/unloads. Patch 1 is a small required improvement; patch 2 is the
actual implementation.
The problem can be reproduced like this:
# while true; do rmmod loop; modprobe loop; done &
# while trace-cmd record -p function_graph /bin/true; do :; done
plugin 'function_graph'
libtracecmd: Invalid argument
error in size of file '/proc/kallsyms'
trace-cmd: Invalid argument
Error creating output file
Best regards,
Ilya
Ilya Leoshkevich (2):
libtracecmd: Support querying position within a new compressed block
libtracecmd: Support changing /proc/kallsyms
lib/trace-cmd/trace-compress.c | 5 ++++-
lib/trace-cmd/trace-output.c | 38 +++++++++++++++++++++++++++++++++-
2 files changed, 41 insertions(+), 2 deletions(-)
--
2.50.1
next reply other threads:[~2025-07-11 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 13:25 Ilya Leoshkevich [this message]
2025-07-11 13:25 ` [PATCH v3 1/2] libtracecmd: Support querying position within a new compressed block Ilya Leoshkevich
2025-07-11 13:25 ` [PATCH v3 2/2] libtracecmd: Support changing /proc/kallsyms Ilya Leoshkevich
2025-08-11 8:22 ` [PATCH v3 0/2] " 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=20250711132802.1781-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 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.