From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>
Cc: Ma Ke <make24@iscas.ac.cn>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
stable@vger.kernel.org, suzuki.poulose@arm.com,
mike.leach@linaro.org, alexander.shishkin@linux.intel.com,
mathieu.poirier@linaro.org
Subject: Re: [PATCH v2 RESEND] coresight: etm-perf: Fix reference count leak in etm_setup_aux
Date: Mon, 15 Dec 2025 09:51:03 +0000 [thread overview]
Message-ID: <20251215095103.GA681384@e132581.arm.com> (raw)
In-Reply-To: <c698d581-da15-42bf-9612-62f1bad66615@linaro.org>
On Mon, Dec 15, 2025 at 11:02:08AM +0200, James Clark wrote:
>
>
> On 15/12/2025 04:27, Ma Ke wrote:
> > In etm_setup_aux(), when a user sink is obtained via
> > coresight_get_sink_by_id(), it increments the reference count of the
> > sink device. However, if the sink is used in path building, the path
> > holds a reference, but the initial reference from
> > coresight_get_sink_by_id() is not released, causing a reference count
> > leak. We should release the initial reference after the path is built.
> >
> > Found by code review.
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 0e6c20517596 ("coresight: etm-perf: Allow an event to use different sinks")
> > Signed-off-by: Ma Ke <make24@iscas.ac.cn>
> > ---
> > Changes in v2:
> > - modified the patch as suggestions.
>
> I think Leo's comment on the previous v2 is still unaddressed. But releasing
> it in coresight_get_sink_by_id() would make it consistent with
> coresight_find_csdev_by_fwnode() and prevent further mistakes.
The point is the coresight core layer uses coresight_grab_device() to
increase the device's refcnt. This is why we don't need to grab a
device when setup AUX.
> It also leads me to see that users of coresight_find_device_by_fwnode()
> should also release it, but only one out of two appears to.
Good finding!
Thanks,
Leo
next prev parent reply other threads:[~2025-12-15 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 2:27 Ma Ke
2025-12-15 9:02 ` James Clark
2025-12-15 9:51 ` Leo Yan [this message]
2025-12-15 10:09 ` Jie Gan
2025-12-19 2:39 ` Ma Ke
2025-12-19 9:41 ` Leo Yan
2025-12-19 9:59 ` Suzuki K Poulose
2025-12-19 11:38 ` Leo Yan
2025-12-19 11:48 ` Suzuki K Poulose
2025-12-19 12:17 ` Leo Yan
2025-12-15 2:38 Ma Ke
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=20251215095103.GA681384@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@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
all inboxes | Powered by JetHome®