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()
----
kernel/trace/trace_events_filter.c | 5 ++++-
kernel/trace/trace_events_trigger.c | 6 ++++--
2 files changed, 8 insertions(+), 3 deletions(-)
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 <[email protected]>
Thanks,
Tom
> ----
> kernel/trace/trace_events_filter.c | 5 ++++-
> kernel/trace/trace_events_trigger.c | 6 ++++--
> 2 files changed, 8 insertions(+), 3 deletions(-)
On Tue, 11 Dec 2018 10:40:19 -0600
Tom Zanussi <[email protected]> wrote:
> 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 <[email protected]>
>
>
Thanks a lot Tom!
-- Steve