From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org,
Tom Zanussi <zanussi@kernel.org>
Subject: [PATCH 0/7] tracing: Misc bugfixes
Date: Thu, 27 Jan 2022 15:44:14 -0600 [thread overview]
Message-ID: <cover.1643319703.git.zanussi@kernel.org> (raw)
Hi Steve,
This is an assorted bunch of bugfixes addressing a bugzilla bug,
smatch warnings, and related things I found while fixing those. In
particular, when looking at the bugzilla bug,
https://bugzilla.kernel.org/show_bug.cgi?id=215513, I noticed that the
err_log output looked truncated and looking further into it found that
it was, because the hist trigger command was very long, exceeding the
256 character limit.
Obviously that's too short, and the final 3 patches remove that
limitation.
Tom
The following changes since commit 4798f3784b1208138e06ab2de65666c19d51ab4d:
tools/tracing: Update Makefile to build rtla (2022-01-27 11:47:17 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/misc-bugfixes-v1
Tom Zanussi (7):
tracing: Fix smatch warning for null glob in
event_hist_trigger_parse()
tracing: Fix smatch warning for do while check in
event_hist_trigger_parse()
tracing: Propagate is_signed to expression
tracing: Don't inc err_log entry count if entry allocation fails
tracing: Remove size restriction on tracing_log_err cmd strings
tracing: Remove size restriction on hist trigger cmd error logging
tracing: Remove size restriction on synthetic event cmd error logging
kernel/trace/trace.c | 56 ++++++++++++++++++++++++-------
kernel/trace/trace.h | 2 +-
kernel/trace/trace_events_hist.c | 39 ++++++++++++++++-----
kernel/trace/trace_events_synth.c | 17 ++++++++--
4 files changed, 88 insertions(+), 26 deletions(-)
--
2.17.1
next reply other threads:[~2022-01-27 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 21:44 Tom Zanussi [this message]
2022-01-27 21:44 ` [PATCH 1/7] tracing: Fix smatch warning for null glob in event_hist_trigger_parse() Tom Zanussi
2022-01-27 21:44 ` [PATCH 2/7] tracing: Fix smatch warning for do while check " Tom Zanussi
2022-01-27 21:44 ` [PATCH 3/7] tracing: Propagate is_signed to expression Tom Zanussi
2022-01-27 21:44 ` [PATCH 4/7] tracing: Don't inc err_log entry count if entry allocation fails Tom Zanussi
2022-01-27 21:44 ` [PATCH 5/7] tracing: Remove size restriction on tracing_log_err cmd strings Tom Zanussi
2022-01-27 21:44 ` [PATCH 6/7] tracing: Remove size restriction on hist trigger cmd error logging Tom Zanussi
2022-01-27 21:44 ` [PATCH 7/7] tracing: Remove size restriction on synthetic event " Tom Zanussi
2022-01-27 23:26 ` [PATCH 0/7] tracing: Misc bugfixes Steven Rostedt
2022-01-27 23:50 ` Tom Zanussi
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=cover.1643319703.git.zanussi@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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.