From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
James Clark <james.clark@linaro.org>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mike Leach <mike.leach@arm.com>,
Leo Yan <leo.yan@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] coresight: fix resource leaks on path build failure
Date: Tue, 10 Nov 2026 09:23:45 +0800 [thread overview]
Message-ID: <3a734370-6961-45da-9af2-0a5fffb1ee9f@oss.qualcomm.com> (raw)
In-Reply-To: <a7a484d0-9458-4051-aad0-983341dfb0e6@arm.com>
On 11/9/2026 7:46 PM, Suzuki K Poulose wrote:
> On 09/11/2026 10:34, James Clark wrote:
>>
>>
>> On 09/11/2026 01:24, Jie Gan wrote:
>>>
>>>
>>> On 5/13/2026 9:32 AM, Jie Gan wrote:
>>>> Two related leaks when _coresight_build_path() encounters an error
>>>> after
>>>> coresight_grab_device() has already incremented the pm_runtime, module,
>>>> and device references for a node:
>>>>
>>>> 1. In _coresight_build_path(), if kzalloc_obj() for the path node fails
>>>> after coresight_grab_device() succeeds, coresight_drop_device() was
>>>> never called, permanently leaking all three references.
>>>>
>>>> 2. In coresight_build_path(), on failure the partial path was freed
>>>> with
>>>> kfree(path) instead of coresight_release_path(path). kfree() only
>>>> frees the coresight_path struct itself; it does not iterate
>>>> path_list
>>>> to call coresight_drop_device() and kfree() for each coresight_node
>>>> already added by deeper recursive calls, leaking both the
>>>> pm_runtime,
>>>> module, and device references and the node memory for every element
>>>> on the partial path.
>>>>
>>>> Fix both by adding coresight_drop_device() in the OOM unwind of
>>>> _coresight_build_path(), and replacing kfree(path) with
>>>> coresight_release_path(path) in coresight_build_path().
>>>>
>>>> Fixes: 32b0707a4182 ("coresight: Add try_get_module() in
>>>> coresight_grab_device()")
>>>> Fixes: b3e94405941e ("coresight: associating path with session
>>>> rather than tracer")
>>>> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
>>>
>>> Gentle ping.
>>>
>>>> ---
>>>> drivers/hwtracing/coresight/coresight-core.c | 6 ++++--
>>>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/hwtracing/coresight/coresight-core.c b/drivers/
>>>> hwtracing/coresight/coresight-core.c
>>>> index 46f247f73cf6..c1354ea8e11d 100644
>>>> --- a/drivers/hwtracing/coresight/coresight-core.c
>>>> +++ b/drivers/hwtracing/coresight/coresight-core.c
>>>> @@ -825,8 +825,10 @@ static int _coresight_build_path(struct
>>>> coresight_device *csdev,
>>>> return ret;
>>>> node = kzalloc_obj(struct coresight_node);
>>>> - if (!node)
>>>> + if (!node) {
>>>> + coresight_drop_device(csdev);
>>>> return -ENOMEM;
>>>> + }
>>>> node->csdev = csdev;
>>>> list_add(&node->link, &path->path_list);
>>>> @@ -851,7 +853,7 @@ struct coresight_path
>>>> *coresight_build_path(struct coresight_device *source,
>>>> rc = _coresight_build_path(source, source, sink, path);
>>>> if (rc) {
>>>> - kfree(path);
>>>> + coresight_release_path(path);
>>
>> @Suzuki, there's a conflict here. This will need to be
>> coresight_release_path_locked() if we also take "coresight: etm-perf:
>> Serialize AUX topology access" from my Sashiko fixes.
>
> The changes needed by the patch are already what your patches does.
> Apologies Jie Gan, I have merged Jamess series which solves everything.
> So, we can ignore this one.
Got it. Glad to hear the issue to be fixed.
Thanks,
Jie
>
> Cheers
> Suzuki
>
prev parent reply other threads:[~2026-11-10 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 1:32 Jie Gan
2026-05-19 13:57 ` James Clark
2026-05-20 1:55 ` Jie Gan
2026-05-20 8:38 ` James Clark
2026-05-20 9:27 ` Mike Leach
2026-05-20 10:13 ` Jie Gan
2026-05-20 15:31 ` James Clark
2026-11-09 1:24 ` Jie Gan
2026-11-09 10:34 ` James Clark
2026-11-09 11:46 ` Suzuki K Poulose
2026-11-10 1:23 ` Jie Gan [this message]
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=3a734370-6961-45da-9af2-0a5fffb1ee9f@oss.qualcomm.com \
--to=jie.gan@oss.qualcomm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tingwei.zhang@oss.qualcomm.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®