mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] tracing: Fix a couple of memory leaks in the event trigger code
Date: Tue, 11 Dec 2018 10:40:19 -0600	[thread overview]
Message-ID: <1913c8d0be777a59d59135c067abf270b0594c63.camel@linux.intel.com> (raw)
In-Reply-To: <20181210204126.603121253@goodmis.org>

Hi Steve,

On Mon, 2018-12-10 at 15:41 -0500, Steven Rostedt wrote:
> Tom,
> 
> While testing other changes, kmemleak pointed out a few leaks in the
> trigger code. Can you take a look at them and give me a Reviewed-by
> or Ack.
> 
> Thanks!
> 
> -- Steve
> 
> 
> Steven Rostedt (VMware) (2):
>       tracing: Fix memory leak in create_filter()
>       tracing: Fix memory leak in set_trigger_filter()
> 

Sure, these look fine to me.

Reviewed-by: Tom Zanussi <tom.zanussi@linux.intel.com>

Thanks,

Tom

> ----
>  kernel/trace/trace_events_filter.c  | 5 ++++-
>  kernel/trace/trace_events_trigger.c | 6 ++++--
>  2 files changed, 8 insertions(+), 3 deletions(-)


  parent reply	other threads:[~2018-12-11 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 20:41 Steven Rostedt
2018-12-10 20:41 ` [PATCH 1/2] tracing: Fix memory leak in create_filter() Steven Rostedt
2018-12-10 20:41 ` [PATCH 2/2] tracing: Fix memory leak in set_trigger_filter() Steven Rostedt
2018-12-11 16:40 ` Tom Zanussi [this message]
2018-12-11 17:46   ` [PATCH 0/2] tracing: Fix a couple of memory leaks in the event trigger code 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=1913c8d0be777a59d59135c067abf270b0594c63.camel@linux.intel.com \
    --to=tom.zanussi@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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
all inboxes | Powered by JetHome®