[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <170905469229.501091.5601373719556598823.b4-ty@kernel.org>
Date: Tue, 27 Feb 2024 09:26:38 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Mark Rutland <mark.rutland@....com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Ian Rogers <irogers@...gle.com>
Cc: linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH] perf pmu: Fix a potential memory leak in perf_pmu__lookup()
On Sat, 26 Aug 2023 23:32:45 +0200, Christophe JAILLET wrote:
> The commit in Fixes has reordered some code, but missed an error handling
> path.
>
> 'goto err' now, in order to avoid a memory leak in case of error.
>
>
Applied to perf-tools-next, thanks!
Best regards,
--
Namhyung Kim <namhyung@...nel.org>
Powered by blists - more mailing lists