From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3] [GIT PULL] tracing: Various memory leak fixes
Date: Tue, 11 Dec 2018 13:54:56 -0500 [thread overview]
Message-ID: <20181211185456.070244180@goodmis.org> (raw)
Linus,
While running various ftrace tests on new development code, the kmemleak
detector found some allocations that were not freed correctly.
This fixes a couple of leaks in the event trigger code as well as
in adding function trace filters in trace instances.
Please pull the latest trace-v4.20-rc6 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.20-rc6
Tag SHA1: 4e790ad722f2a0e23f8e36f307c23b07924235ed
Head SHA1: 2840f84f74035e5a535959d5f17269c69fa6edc5
Steven Rostedt (VMware) (3):
tracing: Fix memory leak in create_filter()
tracing: Fix memory leak in set_trigger_filter()
tracing: Fix memory leak of instance function hash filters
----
kernel/trace/ftrace.c | 1 +
kernel/trace/trace_events_filter.c | 5 ++++-
kernel/trace/trace_events_trigger.c | 6 ++++--
3 files changed, 9 insertions(+), 3 deletions(-)
next reply other threads:[~2018-12-11 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 18:54 Steven Rostedt [this message]
2018-12-11 18:54 ` [PATCH 1/3] tracing: Fix memory leak in create_filter() Steven Rostedt
2018-12-11 18:54 ` [PATCH 2/3] tracing: Fix memory leak in set_trigger_filter() Steven Rostedt
2018-12-11 18:54 ` [PATCH 3/3] tracing: Fix memory leak of instance function hash filters 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=20181211185456.070244180@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome