[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174967824864.435639.16301685333442078712.b4-ty@kernel.org>
Date: Wed, 11 Jun 2025 14:44:08 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...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>, James Clark <james.clark@...aro.org>,
Howard Chu <howardchu95@...il.com>, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org, Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH v1] perf thread: Ensure comm_lock held for comm_list
On Thu, 29 May 2025 12:22:06 -0700, Ian Rogers wrote:
> Add thread safety annotations for comm_list and add locking for two
> instances where the list is accessed without the lock held (in
> contradiction to ____thread__set_comm()).
>
>
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
Powered by blists - more mailing lists