From: Dave Jiang <dave.jiang@intel.com>
To: Tuo Li <islituo@gmail.com>, vinicius.gomes@intel.com, vkoul@kernel.org
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc()
Date: Tue, 6 Jan 2026 08:37:35 -0700 [thread overview]
Message-ID: <b892c320-3138-4689-8a10-12e365961e63@intel.com> (raw)
In-Reply-To: <20260106032428.162445-1-islituo@gmail.com>
On 1/5/26 8:24 PM, Tuo Li wrote:
> At the end of this function, d is the traversal cursor of flist, but the
> code completes found instead. This can lead to issues such as NULL pointer
> dereferences, double completion, or descriptor leaks.
>
> Fix this by completing d instead of found in the final
> list_for_each_entry_safe() loop.
>
> Fixes: aa8d18becc0c ("dmaengine: idxd: add callback support for iaa crypto")
> Signed-off-by: Tuo Li <islituo@gmail.com>
Good catch! Thanks.
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dma/idxd/submit.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/idxd/submit.c b/drivers/dma/idxd/submit.c
> index 6db1c5fcedc5..03217041b8b3 100644
> --- a/drivers/dma/idxd/submit.c
> +++ b/drivers/dma/idxd/submit.c
> @@ -138,7 +138,7 @@ static void llist_abort_desc(struct idxd_wq *wq, struct idxd_irq_entry *ie,
> */
> list_for_each_entry_safe(d, t, &flist, list) {
> list_del_init(&d->list);
> - idxd_dma_complete_txd(found, IDXD_COMPLETE_ABORT, true,
> + idxd_dma_complete_txd(d, IDXD_COMPLETE_ABORT, true,
> NULL, NULL);
> }
> }
next prev parent reply other threads:[~2026-01-06 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 3:24 [PATCH] dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc() Tuo Li
2026-01-06 15:37 ` Dave Jiang [this message]
2026-03-09 11:41 ` 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=b892c320-3138-4689-8a10-12e365961e63@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=islituo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vkoul@kernel.org \
/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