Re: [PATCH] perf trace: Fix potential USE_AFTER_FREE problem

2019-02-14 Thread Jiri Olsa
On Thu, Feb 14, 2019 at 05:22:39AM -0500, YU Bo wrote: > Hi, > On Thu, Feb 14, 2019 at 09:34:11AM +0100, Jiri Olsa wrote: > > On Thu, Feb 14, 2019 at 12:23:56AM -0500, Bo YU wrote: > > > From: Bo Yu > > > > > > There is a freed pointer "evsel", so fix it. > > > > > > Detected by CoverityScan, CI

Re: [PATCH] perf trace: Fix potential USE_AFTER_FREE problem

2019-02-14 Thread YU Bo
Hi, On Thu, Feb 14, 2019 at 09:34:11AM +0100, Jiri Olsa wrote: On Thu, Feb 14, 2019 at 12:23:56AM -0500, Bo YU wrote: From: Bo Yu There is a freed pointer "evsel", so fix it. Detected by CoverityScan, CID#1442595("Memory-illegalaccesses (USE_AFTER_FREE)") Fixes: 6ab3bc240ade4("perf trace: Sup

Re: [PATCH] perf trace: Fix potential USE_AFTER_FREE problem

2019-02-14 Thread Jiri Olsa
On Thu, Feb 14, 2019 at 12:23:56AM -0500, Bo YU wrote: > From: Bo Yu > > There is a freed pointer "evsel", so fix it. > > Detected by CoverityScan, CID#1442595("Memory-illegalaccesses > (USE_AFTER_FREE)") > Fixes: 6ab3bc240ade4("perf trace: Support multiple "vfs_getname" probes") > > Signed-off

[PATCH] perf trace: Fix potential USE_AFTER_FREE problem

2019-02-13 Thread Bo YU
From: Bo Yu There is a freed pointer "evsel", so fix it. Detected by CoverityScan, CID#1442595("Memory-illegalaccesses (USE_AFTER_FREE)") Fixes: 6ab3bc240ade4("perf trace: Support multiple "vfs_getname" probes") Signed-off-by: Bo Yu --- tools/perf/builtin-trace.c | 2 +- 1 file changed, 1 ins