From: Dinh Nguyen <dinguyen@kernel.org>
To: tien.sung.ang@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] firmware: stratix10-svc: fix bug in saving controller data
Date: Thu, 22 Jun 2023 07:02:56 -0500 [thread overview]
Message-ID: <fc0af540-37fb-d2ac-3e3d-e0cb43747e69@kernel.org> (raw)
In-Reply-To: <20230621064645.1431883-3-tien.sung.ang@intel.com>
Again, I asked you base this patch 1st! That way I can send this patch
only to Greg KH. The patch to support N SVC clients need more time.
Dinh
On 6/21/23 01:46, tien.sung.ang@intel.com wrote:
> From: Ang Tien Sung <tien.sung.ang@intel.com>
>
> Fix the incorrect usage of platform_set_drvdata and dev_set_drvdata.
> They both are of the same data and overrides each other. This resulted
> in the rmmod of the svc driver to fail and throw a kernel panic
> for kthread_stop and fifo free.
>
> Fixes: b5dc75c915cd ("firmware: stratix10-svc: extend svc to support new RSU features")
> Signed-off-by: Ang Tien Sung <tien.sung.ang@intel.com>
> ---
> drivers/firmware/stratix10-svc.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/firmware/stratix10-svc.c b/drivers/firmware/stratix10-svc.c
> index ca713f39107e..60e08987c402 100644
> --- a/drivers/firmware/stratix10-svc.c
> +++ b/drivers/firmware/stratix10-svc.c
> @@ -130,6 +130,7 @@ struct stratix10_svc_data {
> * @complete_status: state for completion
> * @invoke_fn: function to issue secure monitor call or hypervisor call
> * @sdm_lock: a mutex lock to allow only one pending sdm message per client
> + * @svc: manages the list of client svc drivers
> *
> * This struct is used to create communication channels for service clients, to
> * handle secure monitor or hypervisor call.
> @@ -144,6 +145,7 @@ struct stratix10_svc_controller {
> svc_invoke_fn *invoke_fn;
> /* Enforces atomic command sending to SDM */
> struct mutex *sdm_lock;
> + struct stratix10_svc *svc;
> };
>
> /**
> @@ -1252,6 +1254,7 @@ static int stratix10_svc_drv_probe(struct platform_device *pdev)
> ret = -ENOMEM;
> goto err_free_kfifo;
> }
> + controller->svc = svc;
>
> svc->stratix10_svc_rsu = platform_device_alloc(STRATIX10_RSU, 0);
> if (!svc->stratix10_svc_rsu) {
> @@ -1279,8 +1282,6 @@ static int stratix10_svc_drv_probe(struct platform_device *pdev)
> goto err_unregister_dev;
> }
>
> - dev_set_drvdata(dev, svc);
> -
> pr_info("Intel Service Layer Driver Initialized\n");
>
> return 0;
> @@ -1296,8 +1297,8 @@ static int stratix10_svc_drv_probe(struct platform_device *pdev)
>
> static int stratix10_svc_drv_remove(struct platform_device *pdev)
> {
> - struct stratix10_svc *svc = dev_get_drvdata(&pdev->dev);
> struct stratix10_svc_controller *ctrl = platform_get_drvdata(pdev);
> + struct stratix10_svc *svc = ctrl->svc;
>
> platform_device_unregister(svc->intel_svc_fcs);
> platform_device_unregister(svc->stratix10_svc_rsu);
prev parent reply other threads:[~2023-06-22 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 6:46 [PATCH v2 0/2] firmware: stratix10-svc: support N clients tien.sung.ang
2023-06-21 6:46 ` [PATCH v2 1/2] firmware: stratix10-svc: Support up to N SVC clients tien.sung.ang
2023-06-21 6:46 ` [PATCH v2 2/2] firmware: stratix10-svc: fix bug in saving controller data tien.sung.ang
2023-06-22 12:02 ` Dinh Nguyen [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=fc0af540-37fb-d2ac-3e3d-e0cb43747e69@kernel.org \
--to=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tien.sung.ang@intel.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