Re: [PATCH v3 1/2] perf tools: Fix potential memory leaks in perf events parser

From: Markus Elfring
Date: Mon Jun 15 2020 - 04:46:03 EST

Next message: Geliang Tang: "Re: [PATCH] mptcp: unify MPTCP_PM_MAX_ADDR and MPTCP_PM_ADDR_MAX"
Previous message: Jan Kiszka: "[PATCH v2 0/2] gpio: Add support for the PCAL9535"
In reply to: Chen Wandun: "[PATCH next v3 1/2] perf tools: fix potential memleak in perf events parser"
Next in thread: Markus Elfring: "Re: [PATCH v3 0/2] Fixing memory leaks in perf events parser"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Fix memory leak of in function parse_events_term__sym_hw()
> and parse_events_term__clone() when string duplication failed.

Can a wording like âFix memory leaks in ââ be more appropriate for
the final commit message?
Would you find any other description variant more pleasing?

Regards,
Markus

Next message: Geliang Tang: "Re: [PATCH] mptcp: unify MPTCP_PM_MAX_ADDR and MPTCP_PM_ADDR_MAX"
Previous message: Jan Kiszka: "[PATCH v2 0/2] gpio: Add support for the PCAL9535"
In reply to: Chen Wandun: "[PATCH next v3 1/2] perf tools: fix potential memleak in perf events parser"
Next in thread: Markus Elfring: "Re: [PATCH v3 0/2] Fixing memory leaks in perf events parser"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]