From: Greg KH <gregkh@linuxfoundation.org>
To: Ian Klatzco <iklatzco@gmail.com>
Cc: stable@vger.kernel.org, yeoreum.yun@arm.com, sashal@kernel.org,
peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: stable: please backport 3b7a34aebbdf to 6.{6,12,13,14,15}.y ("perf: Fix dangling cgroup pointer in cpuctx")
Date: Thu, 28 May 2026 09:31:19 +0200 [thread overview]
Message-ID: <2026052848-gangly-pound-2b1f@gregkh> (raw)
In-Reply-To: <CAB=irMzhVj6B=T6XS7VyN9K_5Q+gCHD7dsw7fKSPWuNfjEATvA@mail.gmail.com>
On Wed, May 27, 2026 at 05:25:13PM -0700, Ian Klatzco wrote:
> Hi all,
>
> linux-6.12.y has the regression commit e9c928807239 ("perf/core: Fix
> child_total_time_enabled accounting bug at task exit", backport of
> mainline a3c3c6667) but is missing the follow-up fix commit 3b7a34aebbdf
> ("perf: Fix dangling cgroup pointer in cpuctx", Yeoreum Yun, mainline
> v6.16-rc).
>
> The following branches are impacted:
>
> linux-6.6.y
> linux-6.12.y
> linux-6.13.y
> linux-6.14.y
> linux-6.15.y
>
> The regression silently bypasses perf_cgroup_event_disable() on the
> event-removal path when the event is non-ACTIVE at close time, leaving
> cpuctx->cgrp dangling at a soon-to-be-freed perf_cgroup struct. See
> 3b7a34aebbdf's commit message for the precise description.
>
> The minimum viable patch is as follows:
>
> @@ in __perf_remove_from_context, after event_sched_out(...):
> + if (event->state > PERF_EVENT_STATE_OFF)
> + perf_cgroup_event_disable(event, ctx);
> +
>
> I can prepare per-branch backports if useful; please let me know.
Please send backports for the trees we currently support (as listed on
the front page of kernel.org).
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-28 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 0:25 stable: please backport 3b7a34aebbdf to 6.{6,12,13,14,15}.y ("perf: Fix dangling cgroup pointer in cpuctx") Ian Klatzco
2026-05-28 7:31 ` Greg KH [this message]
2026-05-29 6:06 ` [PATCH 6.12.y] perf: Fix dangling cgroup pointer in cpuctx Ian Klatzco
2026-05-29 6:06 ` [PATCH 6.6.y] " Ian Klatzco
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=2026052848-gangly-pound-2b1f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=iklatzco@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yeoreum.yun@arm.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