From: Namhyung Kim <namhyung@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] perf/core: Fix a refcount leak in attach_perf_ctx_data()
Date: Tue, 22 Sep 2026 21:47:21 -0700 [thread overview]
Message-ID: <arNZ2YeL7Uuva-YQ@google.com> (raw)
In-Reply-To: <20260922133835.GZ4121339@noisy.programming.kicks-ass.net>
On Tue, Sep 22, 2026 at 03:38:35PM +0200, Peter Zijlstra wrote:
> On Sun, Sep 20, 2026 at 04:16:39PM -0700, Namhyung Kim wrote:
> > The attach_perf_ctx_data() can race on global and !global cases. The
> > global case is protected by global_ctx_data_rwsem and shares a single
> > reference count using perf_ctx_data.global field.
> >
> > But when it races with !global case, it may miss to set the global field
> > and result in a reference count leak.
> >
> > CPU1 CPU2
> > ----------------------------------------------------------------
> > attach_task_ctx_data(global=1) attach_task_ctx_data(global=0)
> > cd1 = alloc_perf_ctx_data() cd2 = alloc_perf_ctx_data()
> > try_cmpxchg() // ok
> > // task->perf_ctx_data = cd2
> >
> > try_cmpxchg() // fail; old = cd2; global = 0
> > refcount_inc_not_zero() // cd2->refcount++;
> > free_perf_ctx_data() // cd1
>
> Urgh, took a good while to remember how all that worked. Also, I think
> it might have been clearer written like so:
>
> CPU1 CPU2
>
> attach_task_ctx_data(.global=1) attach_task_ctx_data(.global=0)
> cd1 = alloc_perf_ctx_data(); cd2 = alloc_perf_ctx_data();
> // { .global = 0, .refcount = 1 };
>
> try_cmpxchg(); // success,
> // task->perf_ctx_data = cd2
> try_cmpxhg(); // fail; old = cd2
> refcount_inc_not_zero(&old->refcount); // success
> // old.refcount = 2
> free_perf_ctx_data(cd1);
I see. I'll do better next time. Let me know if you want me to resend.
Thanks,
Namhyung
>
> > Then later detach_global_ctx_data() will see the data but it's not
> > marked as global, so it won't call detach_task_ctx_data().
> >
> > Fixes: 506e64e710ff ("perf: attach/detach PMU specific data")
> > Assisted-by: Sashiko.dev:Gemini-3.1-pro
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > kernel/events/core.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index db7b76d6b68aa55d..e180134bad5e0ae3 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -5454,6 +5454,8 @@ attach_task_ctx_data(struct task_struct *task, struct kmem_cache *ctx_cache,
> > }
> >
> > if (refcount_inc_not_zero(&old->refcount)) {
> > + if (global)
> > + old->global = true;
> > free_perf_ctx_data(cd); /* unused */
> > return 0;
> > }
>
>
next prev parent reply other threads:[~2026-09-23 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 23:16 Namhyung Kim
2026-09-22 13:38 ` Peter Zijlstra
2026-09-23 4:47 ` Namhyung Kim [this message]
2026-09-23 7:51 ` Peter Zijlstra
2026-09-23 9:52 ` [tip: perf/urgent] " tip-bot2 for Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2026-06-15 5:11 [PATCH RESEND] " Namhyung Kim
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=arNZ2YeL7Uuva-YQ@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®