On Fri, 02 May 2025 15:15:52 +0200 Paul Cacheux via B4 Relay <[email protected]> wrote:
> From: Paul Cacheux <[email protected]> > > Make sure trace_probe_log_clear is called in the tracing > eprobe code path, matching the trace_probe_log_init call. > > Signed-off-by: Paul Cacheux <[email protected]> Looks good to me. Fixes: 7491e2c44278 ("tracing: Add a probe that attaches to trace events") Cc: [email protected] Thank you, > --- > kernel/trace/trace_eprobe.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/kernel/trace/trace_eprobe.c b/kernel/trace/trace_eprobe.c > index > c08355c3ef32b4124ac944d7e3a03efb66492269..916555f0de811f03feed9d923c63078b0e4c993b > 100644 > --- a/kernel/trace/trace_eprobe.c > +++ b/kernel/trace/trace_eprobe.c > @@ -969,10 +969,13 @@ static int __trace_eprobe_create(int argc, const char > *argv[]) > goto error; > } > } > + trace_probe_log_clear(); > return ret; > + > parse_error: > ret = -EINVAL; > error: > + trace_probe_log_clear(); > trace_event_probe_cleanup(ep); > return ret; > } > > -- > 2.49.0 > > -- Masami Hiramatsu (Google) <[email protected]>
