[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250605114118.GC35970@noisy.programming.kicks-ass.net>
Date: Thu, 5 Jun 2025 13:41:18 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Leo Yan <leo.yan@....com>
Cc: Yeoreum Yun <yeoreum.yun@....com>, mingo@...hat.com, mingo@...nel.org,
acme@...nel.org, namhyung@...nel.org, mark.rutland@....com,
alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
irogers@...gle.com, adrian.hunter@...el.com,
kan.liang@...ux.intel.com, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org, David Wang <00107082@....com>
Subject: Re: [PATCH 1/1] perf/core: fix dangling cgroup pointer in cpuctx
On Wed, Jun 04, 2025 at 04:16:40PM +0200, Peter Zijlstra wrote:
Alexander, I just noticed:
> @@ -2183,8 +2184,7 @@ static void perf_put_aux_event(struct perf_event *event)
> * state so that we don't try to schedule it again. Note
> * that perf_event_enable() will clear the ERROR status.
> */
> - event_sched_out(iter, ctx);
> - perf_event_set_state(event, PERF_EVENT_STATE_ERROR);
That this is scheduling out the sibling, and marking the group leader
ERROR; surely this is a mistake?
> + __event_disable(event, ctx, PERF_EVENT_STATE_ERROR);
> }
> }
Powered by blists - more mailing lists