2020-06-15 01:42:32

by Chen Wandun

Subject: [PATCH next v3 0/2] fix potential memleak in perf events parser

fix some memleaks in parse_events_term__sym_hw and parse_events_term__clone.
ls/perf

v1 ==> v2
1. split into two patches
2. add jump targets common exception handling
3. add Fixes tag

v2 ==> v3
add more commit log.

Chen Wandun (1):
perf tools: fix potential memleak in perf events parser

Cheng Jian (1):
perf tools: fix potential memleak in perf events parser

tools/perf/util/parse-events.c | 51 ++++++++++++++++++++++++++++------
1 file changed, 43 insertions(+), 8 deletions(-)

--
2.17.1

2020-06-15 08:33:38

by Markus Elfring

Subject: Re: [PATCH v3 0/2] Fixing memory leaks in perf events parser

> fix some memleaks in parse_events_term__sym_hw and parse_events_term__clone.

Can it be more appropriate to refer to the term “memory leak” in consistent ways?


> v1 ==> v2
> 1. split into two patches

Corresponding development consequences can become more interesting.


> v2 ==> v3
> add more commit log.
>
> Chen Wandun (1):
> perf tools: fix potential memleak in perf events parser
>
> Cheng Jian (1):
> perf tools: fix potential memleak in perf events parser
>
> tools/perf/util/parse-events.c | 51 ++++++++++++++++++++++++++++------

Are there any chances to make the change distinction a bit easier
by adjusting such commit subjects?

Regards,
Markus