Hello,
On Mon, Sep 7, 2020 at 7:31 PM John Garry wrote:
>
> On 07/09/2020 04:45, Namhyung Kim wrote:
> > The aliases were never released causing the following leaks:
> >
> >Indirect leak of 1224 byte(s) in 9 object(s) allocated from:
> > #0 0x7feefb830628 in malloc
> >
On 07/09/2020 14:20, Namhyung Kim wrote:
I also notice that we have other paths like this, where the allocated
pmu (and aliases) are not freed for later error paths, it seems:
parse_events_add_pmu() -> perf_pmu_find() -> pmu_lookup() ->
pmu_add_cpu_aliases().
I had a quick look at the rest of
On 07/09/2020 04:45, Namhyung Kim wrote:
The aliases were never released causing the following leaks:
Indirect leak of 1224 byte(s) in 9 object(s) allocated from:
#0 0x7feefb830628 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x107628)
#1 0x56332c8f1b62 in __perf_pmu__new_alias
The aliases were never released causing the following leaks:
Indirect leak of 1224 byte(s) in 9 object(s) allocated from:
#0 0x7feefb830628 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x107628)
#1 0x56332c8f1b62 in __perf_pmu__new_alias util/pmu.c:322
#2 0x56332c8f401f in
4 matches
Mail list logo