mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Dave Jiang <dave.jiang@intel.com>, Vinod Koul <vkoul@kernel.org>,
	 Frank Li <Frank.Li@kernel.org>, Fenghua Yu <fenghuay@nvidia.com>,
	 Shuai Xue <xueshuai@linux.alibaba.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	 Steve Wahl <steve.wahl@hpe.com>,
	 Bogdan Codres <bogdan.codres@windriver.com>,
	 Zhenzhong Duan <zhenzhong.duan@intel.com>
Subject: [PATCH 0/6] dmaengine: idxd: More error handling fixes
Date: Mon, 12 Oct 2026 14:38:03 -0700	[thread overview]
Message-ID: <20261012-wt-idxd-fixes-v1-0-30a35a445077@intel.com> (raw)

Mostly this series proposes fixes for issues in the error handling
paths of the idxd driver. Patches 1/6, 2/6 and 3/6 are for issues that
have been shown to happen in the real world.

Patch 6/6 is an exception, in the sense that it's not error path
related, it's an issue that I introduced (my scripts were removing
the idxd module after each dmatest run, so I didn't caught this).

Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
---
Steve Wahl (2):
      dmaengine: idxd: Do not call destroy_workqueue with null idxd->wq
      dmaengine: idxd: fix duplicate memory frees on initialization error path

Vinicius Costa Gomes (4):
      dmaengine: idxd: Fix potential double free on probe error path
      dmaengine: idxd: Fix unwind bounds in device registration error paths
      dmaengine: idxd: Fix error code handling in idxd_cdev_open()
      dmaengine: idxd: Do not release interrupt handles on terminate_all

 drivers/dma/idxd/cdev.c   |  8 ++++++--
 drivers/dma/idxd/device.c | 11 ++++++++++-
 drivers/dma/idxd/idxd.h   |  1 +
 drivers/dma/idxd/init.c   | 21 ++++++---------------
 drivers/dma/idxd/irq.c    |  1 +
 drivers/dma/idxd/sysfs.c  |  9 +++++----
 6 files changed, 29 insertions(+), 22 deletions(-)
---
base-commit: 42c31fec1ca76b8b5f7759def122d418dff2cd4b
change-id: 20260803-wt-idxd-fixes-1a06bb69b1e0

Best regards,
--  
Vinicius


             reply	other threads:[~2026-10-12 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 21:38 Vinicius Costa Gomes [this message]
2026-10-12 21:38 ` [PATCH 1/6] dmaengine: idxd: Do not call destroy_workqueue with null idxd->wq Vinicius Costa Gomes
2026-10-12 21:38 ` [PATCH 2/6] dmaengine: idxd: fix duplicate memory frees on initialization error path Vinicius Costa Gomes
2026-10-12 21:38 ` [PATCH 3/6] dmaengine: idxd: Fix potential double free on probe " Vinicius Costa Gomes
2026-10-12 21:38 ` [PATCH 4/6] dmaengine: idxd: Fix unwind bounds in device registration error paths Vinicius Costa Gomes
2026-10-12 21:38 ` [PATCH 5/6] dmaengine: idxd: Fix error code handling in idxd_cdev_open() Vinicius Costa Gomes
2026-10-12 21:38 ` [PATCH 6/6] dmaengine: idxd: Do not release interrupt handles on terminate_all 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=20261012-wt-idxd-fixes-v1-0-30a35a445077@intel.com \
    --to=vinicius.gomes@intel.com \
    --cc=Frank.Li@kernel.org \
    --cc=bogdan.codres@windriver.com \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghuay@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve.wahl@hpe.com \
    --cc=vkoul@kernel.org \
    --cc=xueshuai@linux.alibaba.com \
    --cc=zhenzhong.duan@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®