From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Mao Jinlong <quic_jinlmao@quicinc.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Tingwei Zhang <quic_tingweiz@quicinc.com>,
Yuanfang Zhang <quic_yuanfang@quicinc.com>,
Tao Zhang <quic_taozha@quicinc.com>,
Hao Zhang <quic_hazha@quicinc.com>
Subject: Re: [PATCH v2] coresight: core: Fix coresight device probe failure issue
Date: Tue, 8 Mar 2022 13:36:30 +0000 [thread overview]
Message-ID: <ea6219df-0a10-8e8d-4848-a28704a9f98e@arm.com> (raw)
In-Reply-To: <c77c93bb-f863-47c8-0ba0-3fc63530a9e1@arm.com>
On 08/03/2022 11:56, Suzuki K Poulose wrote:
> Hi Jinlong
>
> On 04/03/2022 08:23, Mao Jinlong wrote:
>> It is possibe that probe failure issue happens when the device
>> and its child_device's probe happens at the same time.
>> In coresight_make_links, has_conns_grp is true for parent, but
>> has_conns_grp is false for child device as has_conns_grp is set
>> to true in coresight_create_conns_sysfs_group. The probe of parent
>> device will fail at this condition. Add has_conns_grp check for
>> child device before make the links and make the process from
>> device_register to connection_create be atomic to avoid this
>> probe failure issue.
>>
>> Suggested-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>> Suggested-by: Mike Leach <mike.leach@linaro.org>
>> Signed-off-by: Mao Jinlong <quic_jinlmao@quicinc.com>
>> ---
>> drivers/hwtracing/coresight/coresight-core.c | 12 ++++++------
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/hwtracing/coresight/coresight-core.c
>> b/drivers/hwtracing/coresight/coresight-core.c
>> index 88653d1c06a4..b3e3bc59c09b 100644
>> --- a/drivers/hwtracing/coresight/coresight-core.c
>> +++ b/drivers/hwtracing/coresight/coresight-core.c
>> @@ -1382,7 +1382,7 @@ static int coresight_fixup_device_conns(struct
>> coresight_device *csdev)
>> continue;
>> conn->child_dev =
>> coresight_find_csdev_by_fwnode(conn->child_fwnode);
>> - if (conn->child_dev) {
>> + if (conn->child_dev && conn->child_dev->has_conns_grp) {
>> ret = coresight_make_links(csdev, conn,
>> conn->child_dev);
>> if (ret)
>> @@ -1594,7 +1594,8 @@ struct coresight_device
>> *coresight_register(struct coresight_desc *desc)
>> refcnts = kcalloc(nr_refcnts, sizeof(*refcnts), GFP_KERNEL);
>> if (!refcnts) {
>> ret = -ENOMEM;
>> - goto err_free_csdev;
>> + kfree(csdev);
>> + goto err_out;
>> }
>> csdev->refcnt = refcnts;
>> @@ -1619,8 +1620,10 @@ struct coresight_device
>> *coresight_register(struct coresight_desc *desc)
>> csdev->dev.fwnode = fwnode_handle_get(dev_fwnode(desc->dev));
>> dev_set_name(&csdev->dev, "%s", desc->name);
>> + mutex_lock(&coresight_mutex);
>> ret = device_register(&csdev->dev);
>> if (ret) {
>> + mutex_unlock(&coresight_mutex);
>> put_device(&csdev->dev);
>> /*
>> * All resources are free'd explicitly via
>> @@ -1634,6 +1637,7 @@ struct coresight_device
>> *coresight_register(struct coresight_desc *desc)
>> ret = etm_perf_add_symlink_sink(csdev);
>> if (ret) {
>> + mutex_unlock(&coresight_mutex);
>> device_unregister(&csdev->dev);
>> /*
>> * As with the above, all resources are free'd
>> @@ -1645,8 +1649,6 @@ struct coresight_device
>> *coresight_register(struct coresight_desc *desc)
>> }
>> }
>> - mutex_lock(&coresight_mutex);
>> -
>> ret = coresight_create_conns_sysfs_group(csdev);
>> if (!ret)
>> ret = coresight_fixup_device_conns(csdev);
>> @@ -1663,8 +1665,6 @@ struct coresight_device
>> *coresight_register(struct coresight_desc *desc)
>> return csdev;
>> -err_free_csdev:
>> - kfree(csdev);
>> err_out:
>> /* Cleanup the connection information */
>> coresight_release_platform_data(NULL, desc->pdata);
>
> Could we consolidate the unlock sequence to a single point with
> something like this (untested):
>
>
> diff --git a/drivers/hwtracing/coresight/coresight-core.c
> b/drivers/hwtracing/coresight/coresight-core.c
> index af00dca8d1ac..198ee140c6e6 100644
> --- a/drivers/hwtracing/coresight/coresight-core.c
> +++ b/drivers/hwtracing/coresight/coresight-core.c
> @@ -1571,6 +1571,7 @@ struct coresight_device *coresight_register(struct
> coresight_desc *desc)
> int nr_refcnts = 1;
> atomic_t *refcnts = NULL;
> struct coresight_device *csdev;
> + bool registered = false;
>
> csdev = kzalloc(sizeof(*csdev), GFP_KERNEL);
> if (!csdev) {
> @@ -1591,7 +1592,8 @@ struct coresight_device *coresight_register(struct
> coresight_desc *desc)
> refcnts = kcalloc(nr_refcnts, sizeof(*refcnts), GFP_KERNEL);
> if (!refcnts) {
> ret = -ENOMEM;
> - goto err_free_csdev;
> + kfree(csdev);
> + goto err_out;
> }
>
> csdev->refcnt = refcnts;
> @@ -1616,6 +1618,13 @@ struct coresight_device
> *coresight_register(struct coresight_desc *desc)
> csdev->dev.fwnode = fwnode_handle_get(dev_fwnode(desc->dev));
> dev_set_name(&csdev->dev, "%s", desc->name);
>
> + /*
> + * Make sure the device registration and the connection fixup
> + * are synchronised, so that we don't see uninitialised devices
> + * on the coresight bus while trying to resolve the connections.
> + */
> + mutex_lock(&coresight_mutex);
> +
> ret = device_register(&csdev->dev);
> if (ret) {
> put_device(&csdev->dev);
> @@ -1623,7 +1632,7 @@ struct coresight_device *coresight_register(struct
> coresight_desc *desc)
> * All resources are free'd explicitly via
> * coresight_device_release(), triggered from put_device().
> */
> - goto err_out;
> + goto out_unlock;
> }
>
> if (csdev->type == CORESIGHT_DEV_TYPE_SINK ||
> @@ -1638,11 +1647,11 @@ struct coresight_device
> *coresight_register(struct coresight_desc *desc)
> * from put_device(), which is in turn called from
> * function device_unregister().
> */
> - goto err_out;
> + goto out_unlock;
> }
> }
> -
> - mutex_lock(&coresight_mutex);
> + /* Device is now registered */
> + registered = true;
>
> ret = coresight_create_conns_sysfs_group(csdev);
> if (!ret)
> @@ -1652,16 +1661,15 @@ struct coresight_device
> *coresight_register(struct coresight_desc *desc)
> if (!ret && cti_assoc_ops && cti_assoc_ops->add)
> cti_assoc_ops->add(csdev);
>
> +out_unlock:
> mutex_unlock(&coresight_mutex);
> - if (ret) {
> + /* Success */
> + if (!ret)
> + return csdev;
> +
> + /* Unregister the device if needed */
> + if (registered)
> coresight_unregister(csdev);
> - return ERR_PTR(ret);
> - }
Apologies, this should be preserved :
i.e,
if (registered) {
coresight_unregister(csdev);
return ERR_PTR(ret);
}
Thanks
Suzuki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-08 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 8:23 [PATCH v2] coresight: core: Fix coresight device probe failure issue Mao Jinlong
2022-03-08 11:56 ` Suzuki K Poulose
2022-03-08 13:36 ` Suzuki K Poulose [this message]
2022-03-09 2:57 ` Jinlong Mao
2022-03-09 14:27 ` Jinlong Mao
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=ea6219df-0a10-8e8d-4848-a28704a9f98e@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=quic_hazha@quicinc.com \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_taozha@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_yuanfang@quicinc.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;
as well as URLs for NNTP newsgroup(s).