From: Fenghua Yu <fenghuay@nvidia.com>
To: Yi Sun <yi.sun@intel.com>,
vinicius.gomes@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: dave.jiang@intel.com, gordon.jin@intel.com
Subject: Re: [PATCH v3 1/2] dmaengine: idxd: Remove improper idxd_free
Date: Tue, 17 Jun 2025 15:13:22 -0700 [thread overview]
Message-ID: <d4b51d33-e46b-448d-b6d3-f0845b1d05f8@nvidia.com> (raw)
In-Reply-To: <20250617102712.727333-2-yi.sun@intel.com>
Hi, Yi,
On 6/17/25 03:27, Yi Sun wrote:
> The call to idxd_free() introduces a duplicate put_device() leading to a
> reference count underflow:
> refcount_t: underflow; use-after-free.
> WARNING: CPU: 15 PID: 4428 at lib/refcount.c:28 refcount_warn_saturate+0xbe/0x110
> ...
> Call Trace:
> <TASK>
> idxd_remove+0xe4/0x120 [idxd]
> pci_device_remove+0x3f/0xb0
> device_release_driver_internal+0x197/0x200
> driver_detach+0x48/0x90
> bus_remove_driver+0x74/0xf0
> pci_unregister_driver+0x2e/0xb0
> idxd_exit_module+0x34/0x7a0 [idxd]
> __do_sys_delete_module.constprop.0+0x183/0x280
> do_syscall_64+0x54/0xd70
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> The idxd_unregister_devices() which is invoked at the very beginning of
> idxd_remove(), already takes care of the necessary put_device() through the
> following call path:
> idxd_unregister_devices() -> device_unregister() -> put_device()
>
> In addition, when CONFIG_DEBUG_KOBJECT_RELEASE is enabled, put_device() may
> trigger asynchronous cleanup via schedule_delayed_work(). If idxd_free() is
> called immediately after, it can result in a use-after-free.
>
> Remove the improper idxd_free() to avoid both the refcount underflow and
> potential memory corruption during module unload.
>
> Fixes: d5449ff1b04d ("dmaengine: idxd: Add missing idxd cleanup to fix memory leak in remove call")
> Signed-off-by: Yi Sun <yi.sun@intel.com>
>
> diff --git a/drivers/dma/idxd/init.c b/drivers/dma/idxd/init.c
> index 80355d03004d..40cc9c070081 100644
> --- a/drivers/dma/idxd/init.c
> +++ b/drivers/dma/idxd/init.c
> @@ -1295,7 +1295,6 @@ static void idxd_remove(struct pci_dev *pdev)
> idxd_cleanup(idxd);
> pci_iounmap(pdev, idxd->reg_base);
> put_device(idxd_confdev(idxd));
> - idxd_free(idxd);
Simply removing idxd_free() causes two issues:
1. This hits memory leak issues because allocated idxd, ida, map are not
freed.
2. There is still an underflow issue for dev refcnt in
idxd_pci_probe_alloc() when idxd_register_devices() fails. Here
get_device() is not called but put_device() is called.
A right fix is to remove the put_device() in idxd_free(). This will fix
all the above issues.
Thanks.
-Fenghua
next prev parent reply other threads:[~2025-06-17 22:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 10:27 [PATCH v3 0/2] dmaengine: idxd: Fix refcount and cleanup issues on module unload Yi Sun
2025-06-17 10:27 ` [PATCH v3 1/2] dmaengine: idxd: Remove improper idxd_free Yi Sun
2025-06-17 22:13 ` Fenghua Yu [this message]
2025-07-27 9:02 ` Yi Sun
2025-07-28 8:21 ` Shuai Xue
2025-06-17 10:27 ` [PATCH v3 2/2] dmaengine: idxd: Fix refcount underflow on module unload Yi Sun
2025-06-17 21:58 ` Fenghua Yu
2025-06-18 0:38 ` Vinicius Costa Gomes
2025-07-27 9:16 ` Yi Sun
2025-07-28 8:40 ` Shuai Xue
2025-07-28 11:43 ` Yi Sun
2025-07-29 2:46 ` Shuai Xue
2025-07-29 3:15 ` Yi Sun
2025-07-29 6:00 ` Shuai Xue
2025-07-31 0:17 ` Vinicius Costa Gomes
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=d4b51d33-e46b-448d-b6d3-f0845b1d05f8@nvidia.com \
--to=fenghuay@nvidia.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gordon.jin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=yi.sun@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;
as well as URLs for NNTP newsgroup(s).