linux-kernel - Re: [PATCH 0/2] tracing: Fix a couple of memory leaks in the event trigger code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1913c8d0be777a59d59135c067abf270b0594c63.camel@linux.intel.com>
Date:   Tue, 11 Dec 2018 10:40:19 -0600
From:   Tom Zanussi <tom.zanussi@...ux.intel.com>
To:     Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org
Cc:     Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/2] tracing: Fix a couple of memory leaks in the event
 trigger code

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@...ux.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(-)