All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bogdan Codres <bogdan.codres@windriver.com>
To: vinicius.gomes@intel.com, steve.wahl@hpe.com
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bogdan Codres <bogdan.codres@windriver.com>
Subject: Re: [PATCH v2 2/2] dmaengine: idxd: fix duplicate memory frees on initialization error path
Date: Mon, 29 Jun 2026 15:11:21 +0300	[thread overview]
Message-ID: <20260629121129.1213335-1-bogdan.codres@windriver.com> (raw)
In-Reply-To: <1782732745-9499-mlmmj-112abde3@vger.kernel.org>

Hi Vinicius, Steve,
Thanks for the heads-up. I'm totally fine with being added as

Reported-by: Bogdan Codres <bogdan.codres@windriver.com>

on Steve's patch — his fix addresses the same issue I was seeing.

You can use my splat ad the reproducer.

Regarding the third patch for the dangling ->wq pointer — the idxd->wq = NULL after destroy_workqueue()
looks reasonable to me.

Best regards, Bogdan

       reply	other threads:[~2026-06-29 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1782732745-9499-mlmmj-112abde3@vger.kernel.org>
2026-06-29 12:11 ` Bogdan Codres [this message]
2026-05-22 20:34 [PATCH v2 1/2] dmaengine: idxd: Do not call destroy_workqueue with null idxd->wq Steve Wahl
2026-05-22 20:34 ` [PATCH v2 2/2] dmaengine: idxd: fix duplicate memory frees on initialization error path Steve Wahl
2026-05-22 22:51   ` sashiko-bot
2026-06-27  0:57   ` Vinicius Costa Gomes
     [not found]     ` <BYAPR11MB36069EC520DCB9DFD6A411EEF8E82@BYAPR11MB3606.namprd11.prod.outlook.com>
     [not found]       ` <BYAPR11MB36068CF244AA0940E39D3B50F8E82@BYAPR11MB3606.namprd11.prod.outlook.com>
2026-06-29 19:02         ` Steve Wahl

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=20260629121129.1213335-1-bogdan.codres@windriver.com \
    --to=bogdan.codres@windriver.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve.wahl@hpe.com \
    --cc=vinicius.gomes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.