[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZruhsN4i6xtc59nJ@x1>
Date: Tue, 13 Aug 2024 15:10:56 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>,
Thomas Richter <tmricht@...ux.ibm.com>,
Kajol Jain <kjain@...ux.ibm.com>,
Athira Rajeev <atrajeev@...ux.vnet.ibm.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/2] perf disasm: Fix memory leak for locked operations
On Tue, Aug 13, 2024 at 09:04:57AM -0700, Ian Rogers wrote:
> On Tue, Aug 13, 2024 at 7:53 AM Arnaldo Carvalho de Melo
> <acme@...nel.org> wrote:
> >
> > On Mon, Aug 12, 2024 at 09:06:12PM -0700, Ian Rogers wrote:
> > > lock__parse calls disasm_line__parse passing
> > > &ops->locked.ins.name. Ensure ops->locked.ins.name is freed in
> > > lock__delete.
> > >
> > > Found with lock/leak sanitizer.
>
> Ooops, I meant address/leak sanitizer.
>
> > Applied both patches to perf-tools-next.
>
> Thanks, could you fix the commit message.
Sure,
- Arnaldo
Powered by blists - more mailing lists