mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Garg, Shivank" <shivankg@amd.com>
To: "vkoul@kernel.org" <vkoul@kernel.org>,
	"Frank.Li@kernel.org" <Frank.Li@kernel.org>,
	"logang@deltatee.com" <logang@deltatee.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"sashiko-bot@kernel.org" <sashiko-bot@kernel.org>,
	"Frank.Li@nxp.com" <Frank.Li@nxp.com>
Subject: Re: [PATCH v4 4/4] dmaengine: wait for RCU readers before releasing dma_device
Date: Tue, 18 Aug 2026 16:44:31 +0000	[thread overview]
Message-ID: <6ae652b864ccf2e56b56b2a541e4b81854879593.camel@amd.com> (raw)
In-Reply-To: <c9e8b7e6-6a3b-4443-8632-81f2a2a4f79d@deltatee.com>

On Tue, 2026-08-18 at 10:21 -0600, Logan Gunthorpe wrote:
> 
> On 2026-08-17 21:43, Shivank Garg wrote:
> > diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
> > index d075051dd187..604c9af19936 100644
> > --- a/drivers/dma/dmaengine.c
> > +++ b/drivers/dma/dmaengine.c
> > @@ -429,6 +429,12 @@ static void dma_device_release(struct kref *ref)
> >  	list_del_rcu(&device->global_node);
> >  	dma_channel_rebalance();
> >  
> > +	/*
> > +	 * Wait for RCU readers (e.g. dma_issue_pending_all()) that may still
> > +	 * be traversing dma_device_list before the device is freed.
> > +	 */
> > +	synchronize_rcu();
> > +
> >  	if (device->device_release)
> >  		device->device_release(device);
> >  }
> > 
> 
> A couple minor points on this:
> 
> 1. I think the comment, as is, isn't useful. It's pretty clear the
> synchronize_rcu() call is paired with the list_del_rcu() call above it.
> 

Sure, I'll drop it.

> 2. The new synchronize_rcu() call will delay for a grace period with the
> dma_list_mutex lock held. Is that okay? It might be, but if so, it could
> use a note in the commit message.
> 

yeah, I believe it is okay as the added latency is confined to only
teardown path. I'll add note.

> Besides that, these are minor points and the patch does fix a real issue so:
> 
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> 
> 

Thanks for the review

Best regards,
Shivank

      reply	other threads:[~2026-08-18 16:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18  3:43 [PATCH v4 0/4] dmaengine: fix kref underflow and UAF in dma_chan_put() Shivank Garg
2026-08-18  3:43 ` [PATCH v4 1/4] dmaengine: add dma_device_get() helper Shivank Garg
2026-08-18 15:44   ` Logan Gunthorpe
2026-08-18 16:12   ` Frank Li
2026-08-18 16:27     ` Garg, Shivank
2026-08-19 15:50       ` Frank Li
2026-08-18  3:43 ` [PATCH v4 2/4] dmaengine: Fix device kref underflow in dma_chan_put() Shivank Garg
2026-08-18 15:49   ` Logan Gunthorpe
2026-08-18  3:43 ` [PATCH v4 3/4] dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() Shivank Garg
2026-08-18 15:50   ` Logan Gunthorpe
2026-08-18  3:43 ` [PATCH v4 4/4] dmaengine: wait for RCU readers before releasing dma_device Shivank Garg
2026-08-18 16:21   ` Logan Gunthorpe
2026-08-18 16:44     ` Garg, Shivank [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=6ae652b864ccf2e56b56b2a541e4b81854879593.camel@amd.com \
    --to=shivankg@amd.com \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=sashiko-bot@kernel.org \
    --cc=stable@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®