From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Yunfeng Ye <yeyunfeng@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
hushiyuan@huawei.com, linfeilong@huawei.com
Subject: Re: [PATCH v2] perf kmem: Fix memory leak in compact_gfp_flags()
Date: Wed, 16 Oct 2019 11:06:51 -0300 [thread overview]
Message-ID: <20191016140651.GF22835@kernel.org> (raw)
In-Reply-To: <7fd48f77-fbc4-b99f-60c1-ccc7d8d287e9@huawei.com>
Em Wed, Oct 16, 2019 at 09:26:50PM +0800, Yunfeng Ye escreveu:
> The memory @orig_flags is allocated by strdup(), it is freed on the
> normal path, but leak to free on the error path.
>
> Fix this by adding free(orig_flags) on the error path.
>
> Fixes: 0e11115644b3 ("perf kmem: Print gfp flags in human readable string")
> Signed-off-by: Yunfeng Ye <yeyunfeng@huawei.com>
> ---
> v1 -> v2:
> - add "Fixes:" message
No need for that, I did it already, just next time look for when the
problem you fixed was introduced, that way the various bots out there
can pick this up for backports, i.e. your fix has a higher chance of
being beneficial to more systems.
- Arnaldo
> tools/perf/builtin-kmem.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/builtin-kmem.c b/tools/perf/builtin-kmem.c
> index 1e61e353f579..9661671cc26e 100644
> --- a/tools/perf/builtin-kmem.c
> +++ b/tools/perf/builtin-kmem.c
> @@ -691,6 +691,7 @@ static char *compact_gfp_flags(char *gfp_flags)
> new = realloc(new_flags, len + strlen(cpt) + 2);
> if (new == NULL) {
> free(new_flags);
> + free(orig_flags);
> return NULL;
> }
>
> --
> 2.7.4.3
--
- Arnaldo
next prev parent reply other threads:[~2019-10-16 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 13:26 [PATCH v2] perf kmem: Fix memory leak in compact_gfp_flags() Yunfeng Ye
2019-10-16 14:06 ` Arnaldo Carvalho de Melo [this message]
2019-10-16 14:19 ` Yunfeng Ye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191016140651.GF22835@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=hushiyuan@huawei.com \
--cc=jolsa@redhat.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yeyunfeng@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox