From: Jingyi Li <jinli@purestorage.com>
To: vkoul@kernel.org, vinicius.gomes@intel.com
Cc: Frank.Li@kernel.org, dave.jiang@intel.com,
xueshuai@linux.alibaba.com, fenghuay@nvidia.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] dmaengine: idxd: fix crashes in the probe error path
Date: Wed, 28 Oct 2026 20:24:25 +0000 [thread overview]
Message-ID: <20261028202425.1144329-1-jinli@purestorage.com> (raw)
In-Reply-To: <20261028003708.834341-1-jinli@purestorage.com>
Hi Frank, Vinod,
Thanks Frank for the review and for pointing me to Vinicius's series
"dmaengine: idxd: More error handling fixes" [1]. Patches 1-3 of that
series cover both patches here:
- 1/2 (double free in idxd_free()) is covered by their 2/6, which
makes the same change to idxd_free().
- 2/2 (destroy of a NULL or already destroyed workqueue) is covered
by their 1/6 and 3/6 together. 1/6 adds the same NULL check in
idxd_conf_device_release(), for a probe failure before idxd->wq is
allocated. 3/6 removes the early destroy_workqueue() calls, so the
release callback is the only place the workqueue is destroyed.
So please drop this series in favor of theirs. The one caveat is that
1/6 alone only covers the "never allocated" case; without 3/6, a
failure after idxd_setup_internals() still destroys the workqueue
twice. If 1/6 and 3/6 don't both go in (including to stable), 2/2
here would still be needed.
I've replied on their series with test results.
[1] https://lore.kernel.org/dmaengine/20261012-wt-idxd-fixes-v1-0-30a35a445077@intel.com/
Thanks,
Jingyi
prev parent reply other threads:[~2026-10-28 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 0:37 Jingyi Li
2026-10-28 0:37 ` [PATCH 1/2] dmaengine: idxd: fix double free in idxd_free() Jingyi Li
2026-10-28 15:04 ` Frank Li
2026-10-28 0:37 ` [PATCH 2/2] dmaengine: idxd: fix destroy of NULL or already destroyed workqueue Jingyi Li
2026-10-28 15:07 ` Frank Li
2026-10-28 20:24 ` Jingyi Li [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=20261028202425.1144329-1-jinli@purestorage.com \
--to=jinli@purestorage.com \
--cc=Frank.Li@kernel.org \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghuay@nvidia.com \
--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
all inboxes | Powered by JetHome®