From: Dave Jiang <dave.jiang@intel.com>
To: Yi Sun <yi.sun@intel.com>,
vinicius.gomes@intel.com, vkoul@kernel.org, fenghuay@nvidia.com,
xueshuai@linux.alibaba.com
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
gordon.jin@intel.com
Subject: Re: [PATCH RESEND v3 0/2] dmaengine: idxd: Fix refcount and cleanup issues on module unload
Date: Tue, 29 Jul 2025 08:06:06 -0700 [thread overview]
Message-ID: <9b1b3405-26a2-4a30-b212-983568deccce@intel.com> (raw)
In-Reply-To: <20250729150313.1934101-1-yi.sun@intel.com>
On 7/29/25 8:03 AM, Yi Sun wrote:
> This patch series addresses two issues related to the device reference
> counting and cleanup path in the idxd driver.
>
> Recent changes introduced improper put_device() calls and duplicated
> cleanup logic, leading to refcount underflow and potential use-after-free
> during module unload.
>
> Patch 1 removes an unnecessary call to idxd_free(), which could result in a
> use-after-free, because the function idxd_conf_device_release already
> covers everything done in idxd_free. The newly added idxd_free in commit
> 90022b3 doesn't resolve any memory leaks, but introduces several duplicated
> cleanup.
>
> Patch 2 refactors the cleanup to avoid redundant put_device() calls
> introduced in commit a409e919ca3. The existing idxd_unregister_devices()
> already handles proper device reference release.
>
> Both patches have been verified on hardware platform.
>
> Both patches have been run through `checkpatch.pl`. Patch 2 gets 1 error
> and 1 warning. But these appear to be limitations in the checkpatch script
> itself, not reflect issues with the patches.
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
for the series
>
> ---
> Changes in V3:
> - Removed function idxd_disable_sva which got removed recently (Vinicius)
> Changes in v2:
> - Reworded commit messages supplementing the call traces (Vinicius)
> - Explain why the put_device are unnecessary. (Vinicius)
>
> Yi Sun (2):
> dmaengine: idxd: Remove improper idxd_free
> dmaengine: idxd: Fix refcount underflow on module unload
>
> drivers/dma/idxd/init.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2025-07-29 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 15:03 [PATCH RESEND v3 0/2] dmaengine: idxd: Fix refcount and cleanup issues on module unload Yi Sun
2025-07-29 15:03 ` [PATCH v3 RESEND 1/2] dmaengine: idxd: Remove improper idxd_free Yi Sun
2025-07-29 15:03 ` [PATCH RESEND v3 2/2] dmaengine: idxd: Fix refcount underflow on module unload Yi Sun
2025-07-29 15:06 ` Dave Jiang [this message]
2025-07-31 1:09 ` [PATCH RESEND v3 0/2] dmaengine: idxd: Fix refcount and cleanup issues " Vinicius Costa Gomes
2025-08-12 2:17 ` Yi Sun
2025-08-12 8:05 ` Lai, Yi
2025-08-20 17:39 ` Vinod Koul
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=9b1b3405-26a2-4a30-b212-983568deccce@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghuay@nvidia.com \
--cc=gordon.jin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vkoul@kernel.org \
--cc=xueshuai@linux.alibaba.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