mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: vinicius.gomes@intel.com, dave.jiang@intel.com,
	fenghuay@nvidia.com,  xueshuai@linux.alibaba.com,
	Yi Sun <yi.sun@intel.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: Wed, 20 Aug 2025 23:09:11 +0530	[thread overview]
Message-ID: <175571155143.80631.2976104483965927036.b4-ty@kernel.org> (raw)
In-Reply-To: <20250729150313.1934101-1-yi.sun@intel.com>


On Tue, 29 Jul 2025 23:03:11 +0800, 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.
> 
> [...]

Applied, thanks!

[1/2] dmaengine: idxd: Remove improper idxd_free
      commit: f41c538881eec4dcf5961a242097d447f848cda6
[2/2] dmaengine: idxd: Fix refcount underflow on module unload
      commit: b7cb9a034305d52222433fad10c3de10204f29e7

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2025-08-20 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 15:03 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 ` [PATCH RESEND v3 0/2] dmaengine: idxd: Fix refcount and cleanup issues " Dave Jiang
2025-07-31  1:09 ` Vinicius Costa Gomes
2025-08-12  2:17   ` Yi Sun
2025-08-12  8:05 ` Lai, Yi
2025-08-20 17:39 ` Vinod Koul [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=175571155143.80631.2976104483965927036.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=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=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

all inboxes | Powered by JetHome®