From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Tom Zanussi <zanussi@kernel.org>,
Xiaoke Wang <xkernel.wang@foxmail.com>
Subject: [for-linus][PATCH 00/10] tracing: Fixes for 5.17-rc1
Date: Fri, 28 Jan 2022 11:18:02 -0500 [thread overview]
Message-ID: <20220128161802.711119424@goodmis.org> (raw)
Tracing fixes for 5.17-rc1:
- Limit mcount build time sorting to only those archs that
we know it works for.
- Fix memory leak in error path of historgam setup
- Fix and clean up rel_loc array out of bounds issue
- tools/rtla documentation fixes
- Fix issues with histogram logic
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
ftrace/urgent
Head SHA1: 67ab5eb71b37b55f7c5522d080a1b42823351776
Kees Cook (1):
tracing/perf: Avoid -Warray-bounds warning for __rel_loc macro
Masami Hiramatsu (1):
tracing: Avoid -Warray-bounds warning for __rel_loc macro
Shuah Khan (2):
rtla: Make doc build optional
tools/tracing: Update Makefile to build rtla
Steven Rostedt (Google) (1):
ftrace: Have architectures opt-in for mcount build time sorting
Tom Zanussi (4):
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
Xiaoke Wang (1):
tracing/histogram: Fix a potential memory leak for kstrdup()
----
arch/arm/Kconfig | 1 +
arch/x86/Kconfig | 1 +
include/trace/perf.h | 5 +++--
include/trace/trace_events.h | 9 +++++----
kernel/trace/Kconfig | 8 +++++++-
kernel/trace/trace.c | 3 ++-
kernel/trace/trace_events_hist.c | 10 ++++++++--
scripts/Makefile | 2 +-
tools/tracing/Makefile | 18 ++++++++++++++----
tools/tracing/rtla/Makefile | 2 +-
10 files changed, 43 insertions(+), 16 deletions(-)
next reply other threads:[~2022-01-28 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 16:18 Steven Rostedt [this message]
2022-01-28 16:18 ` [for-linus][PATCH 01/10] ftrace: Have architectures opt-in for mcount build time sorting Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 02/10] tracing/histogram: Fix a potential memory leak for kstrdup() Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 03/10] tracing: Avoid -Warray-bounds warning for __rel_loc macro Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 04/10] tracing/perf: " Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 05/10] rtla: Make doc build optional Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 06/10] tools/tracing: Update Makefile to build rtla Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 07/10] tracing: Fix smatch warning for null glob in event_hist_trigger_parse() Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 08/10] tracing: Fix smatch warning for do while check " Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 09/10] tracing: Propagate is_signed to expression Steven Rostedt
2022-01-28 16:18 ` [for-linus][PATCH 10/10] tracing: Dont inc err_log entry count if entry allocation fails Steven Rostedt
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=20220128161802.711119424@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=xkernel.wang@foxmail.com \
--cc=zanussi@kernel.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).