From: Fenghua Yu <fenghuay@nvidia.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>,
vinicius.gomes@intel.com, dave.jiang@intel.com,
Markus.Elfring@web.de, vkoul@kernel.org
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/9] dmaengine: idxd: Add missing cleanup for early error out in idxd_setup_internals
Date: Wed, 2 Apr 2025 16:26:40 -0700 [thread overview]
Message-ID: <22b63198-2aab-481c-a4cd-74c3349e22f8@nvidia.com> (raw)
In-Reply-To: <20250309062058.58910-5-xueshuai@linux.alibaba.com>
On 3/8/25 22:20, Shuai Xue wrote:
> The idxd_setup_internals() is missing some cleanup when things fail in
> the middle.
>
> Add the appropriate cleanup routines:
>
> - cleanup groups
> - cleanup enginces
> - cleanup wqs
>
> to make sure it exits gracefully.
>
> Fixes: defe49f96012 ("dmaengine: idxd: fix group conf_dev lifetime")
> Cc: stable@vger.kernel.org
> Suggested-by: Fenghua Yu <fenghuay@nvidia.com>
> Signed-off-by: Shuai Xue <xueshuai@linux.alibaba.com>
> ---
> drivers/dma/idxd/init.c | 59 ++++++++++++++++++++++++++++++++++++-----
> 1 file changed, 52 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/dma/idxd/init.c b/drivers/dma/idxd/init.c
> index fe4a14813bba..7334085939dc 100644
> --- a/drivers/dma/idxd/init.c
> +++ b/drivers/dma/idxd/init.c
> @@ -155,6 +155,26 @@ static void idxd_cleanup_interrupts(struct idxd_device *idxd)
> pci_free_irq_vectors(pdev);
> }
>
> +static void idxd_clean_wqs(struct idxd_device *idxd)
> +{
> + struct idxd_wq *wq;
> + struct device *conf_dev;
> + int i;
> +
> + for (i = 0; i < idxd->max_wqs; i++) {
> + wq = idxd->wqs[i];
> + if (idxd->hw.wq_cap.op_config)
> + bitmap_free(wq->opcap_bmap);
> + kfree(wq->wqcfg);
> + conf_dev = wq_confdev(wq);
> + put_device(conf_dev);
> + kfree(wq);
> +
Please remove this blank line here, warned by checkpatch.
> + }
> + bitmap_free(idxd->wq_enable_map);
> + kfree(idxd->wqs);
> +}
> +
> static int idxd_setup_wqs(struct idxd_device *idxd)
> {
> struct device *dev = &idxd->pdev->dev;
> @@ -245,6 +265,21 @@ static int idxd_setup_wqs(struct idxd_device *idxd)
> return rc;
> }
>
> +static void idxd_clean_engines(struct idxd_device *idxd)
> +{
> + struct idxd_engine *engine;
> + struct device *conf_dev;
> + int i;
> +
> + for (i = 0; i < idxd->max_engines; i++) {
> + engine = idxd->engines[i];
> + conf_dev = engine_confdev(engine);
> + put_device(conf_dev);
> + kfree(engine);
> + }
> + kfree(idxd->engines);
> +}
> +
> static int idxd_setup_engines(struct idxd_device *idxd)
> {
> struct idxd_engine *engine;
> @@ -296,6 +331,19 @@ static int idxd_setup_engines(struct idxd_device *idxd)
> return rc;
> }
>
> +static void idxd_clean_groups(struct idxd_device *idxd)
> +{
> + struct idxd_group *group;
> + int i;
> +
> + for (i = 0; i < idxd->max_groups; i++) {
> + group = idxd->groups[i];
> + put_device(group_confdev(group));
> + kfree(group);
> + }
> + kfree(idxd->groups);
> +}
> +
> static int idxd_setup_groups(struct idxd_device *idxd)
> {
> struct device *dev = &idxd->pdev->dev;
> @@ -410,7 +458,7 @@ static int idxd_init_evl(struct idxd_device *idxd)
> static int idxd_setup_internals(struct idxd_device *idxd)
> {
> struct device *dev = &idxd->pdev->dev;
> - int rc, i;
> + int rc;
>
> init_waitqueue_head(&idxd->cmd_waitq);
>
> @@ -441,14 +489,11 @@ static int idxd_setup_internals(struct idxd_device *idxd)
> err_evl:
> destroy_workqueue(idxd->wq);
> err_wkq_create:
> - for (i = 0; i < idxd->max_groups; i++)
> - put_device(group_confdev(idxd->groups[i]));
> + idxd_clean_groups(idxd);
> err_group:
> - for (i = 0; i < idxd->max_engines; i++)
> - put_device(engine_confdev(idxd->engines[i]));
> + idxd_clean_engines(idxd);
> err_engine:
> - for (i = 0; i < idxd->max_wqs; i++)
> - put_device(wq_confdev(idxd->wqs[i]));
> + idxd_clean_wqs(idxd);
> err_wqs:
> return rc;
> }
Reviewed-by: Fenghua Yu <fenghuay@nvidia.com>
Thanks.
-Fenghua
next prev parent reply other threads:[~2025-04-02 23:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 6:20 [PATCH v3 0/9] dmaengine: idxd: fix memory leak in error handling path Shuai Xue
2025-03-09 6:20 ` [PATCH v3 1/9] dmaengine: idxd: fix memory leak in error handling path of idxd_setup_wqs Shuai Xue
2025-03-09 9:10 ` [PATCH v3 1/9] dmaengine: idxd: fix memory leak in error handling path of idxd_setup_wqs() Markus Elfring
2025-03-10 1:42 ` Shuai Xue
2025-03-10 9:50 ` [v3 " Markus Elfring
2025-04-02 23:22 ` [PATCH v3 1/9] dmaengine: idxd: fix memory leak in error handling path of idxd_setup_wqs Fenghua Yu
2025-03-09 6:20 ` [PATCH v3 2/9] dmaengine: idxd: fix memory leak in error handling path of idxd_setup_engines Shuai Xue
2025-03-09 6:20 ` [PATCH v3 3/9] dmaengine: idxd: fix memory leak in error handling path of idxd_setup_groups Shuai Xue
2025-04-02 23:24 ` Fenghua Yu
2025-03-09 6:20 ` [PATCH v3 4/9] dmaengine: idxd: Add missing cleanup for early error out in idxd_setup_internals Shuai Xue
2025-03-10 15:33 ` Dave Jiang
2025-04-02 23:26 ` Fenghua Yu [this message]
2025-04-04 11:47 ` Shuai Xue
2025-03-09 6:20 ` [PATCH v3 5/9] dmaengine: idxd: Add missing cleanups in cleanup internals Shuai Xue
2025-03-10 15:34 ` Dave Jiang
2025-04-02 23:27 ` Fenghua Yu
2025-03-09 6:20 ` [PATCH v3 6/9] dmaengine: idxd: fix memory leak in error handling path of idxd_alloc Shuai Xue
2025-04-02 23:31 ` Fenghua Yu
2025-03-09 6:20 ` [PATCH v3 7/9] dmaengine: idxd: fix memory leak in error handling path of idxd_pci_probe Shuai Xue
2025-04-02 23:31 ` Fenghua Yu
2025-03-09 6:20 ` [PATCH v3 8/9] dmaengine: idxd: Add missing idxd cleanup to fix memory leak in remove call Shuai Xue
2025-03-10 15:35 ` Dave Jiang
2025-04-02 23:31 ` Fenghua Yu
2025-03-09 6:20 ` [PATCH v3 9/9] dmaengine: idxd: Refactor remove call with idxd_cleanup() helper Shuai Xue
2025-03-10 15:36 ` Dave Jiang
2025-04-02 23:32 ` Fenghua Yu
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=22b63198-2aab-481c-a4cd-74c3349e22f8@nvidia.com \
--to=fenghuay@nvidia.com \
--cc=Markus.Elfring@web.de \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vkoul@kernel.org \
--cc=xueshuai@linux.alibaba.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