From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v3 0/3] Fix listener and add trace file validation
Date: Fri, 26 Feb 2021 06:06:08 +0200 [thread overview]
Message-ID: <20210226040611.186037-1-tz.stoyanov@gmail.com> (raw)
Added checks for trace file consistency when reading and writing it.
Fixed broken tarce-cmd listener.
v3 changes:
- Fixed a comment to be in the Linux style.
- Moved the optimization for disabling trace plugins in its own patch.
v2 changes:
- Converted file states from bitmask to enum
- Added return value of collect_metadata_from_client() to track any errors
Tzvetomir Stoyanov (VMware) (3):
trace-cmd: Add validation for reading and writing trace.dat files
trace-cmd: Do not use trace plugins when reading partial trace files
trace-cmd: Fix broken listener and add error checks
.../include/private/trace-cmd-private.h | 23 ++-
lib/trace-cmd/trace-input.c | 27 +++-
lib/trace-cmd/trace-output.c | 139 +++++++++++++++---
tracecmd/trace-listen.c | 30 ++--
tracecmd/trace-record.c | 33 ++++-
tracecmd/trace-split.c | 2 +-
6 files changed, 202 insertions(+), 52 deletions(-)
--
2.29.2
next reply other threads:[~2021-02-26 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 4:06 Tzvetomir Stoyanov (VMware) [this message]
2021-02-26 4:06 ` [PATCH v3 1/3] trace-cmd: Add validation for reading and writing trace.dat files Tzvetomir Stoyanov (VMware)
2021-02-26 4:06 ` [PATCH v3 2/3] trace-cmd: Do not use trace plugins when reading partial trace files Tzvetomir Stoyanov (VMware)
2021-02-26 4:06 ` [PATCH v3 3/3] trace-cmd: Fix broken listener and add error checks Tzvetomir Stoyanov (VMware)
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=20210226040611.186037-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.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).