From: Dave Jiang <dave.jiang@intel.com>
To: Amelie Delaunay <amelie.delaunay@foss.st.com>,
Vinod Koul <vkoul@kernel.org>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: fix NULL pointer in channel unregistration function
Date: Wed, 13 Dec 2023 09:55:08 -0700 [thread overview]
Message-ID: <be59d5ac-fabb-4a05-99d4-fb281f7ea507@intel.com> (raw)
In-Reply-To: <20231213160452.2598073-1-amelie.delaunay@foss.st.com>
On 12/13/23 09:04, Amelie Delaunay wrote:
> __dma_async_device_channel_register() can fail. In case of failure,
> chan->local is freed (with free_percpu()), and chan->local is nullified.
> When dma_async_device_unregister() is called (because of managed API or
> intentionally by DMA controller driver), channels are unconditionally
> unregistered, leading to this NULL pointer:
> [ 1.318693] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0
> [...]
> [ 1.484499] Call trace:
> [ 1.486930] device_del+0x40/0x394
> [ 1.490314] device_unregister+0x20/0x7c
> [ 1.494220] __dma_async_device_channel_unregister+0x68/0xc0
>
> Look at dma_async_device_register() function error path, channel device
> unregistration is done only if chan->local is not NULL.
>
> Then add the same condition at the beginning of
> __dma_async_device_channel_unregister() function, to avoid NULL pointer
> issue whatever the API used to reach this function.
>
> Fixes: d2fb0a043838 ("dmaengine: break out channel registration")
> Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dma/dmaengine.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
> index b7388ae62d7f..491b22240221 100644
> --- a/drivers/dma/dmaengine.c
> +++ b/drivers/dma/dmaengine.c
> @@ -1103,6 +1103,9 @@ EXPORT_SYMBOL_GPL(dma_async_device_channel_register);
> static void __dma_async_device_channel_unregister(struct dma_device *device,
> struct dma_chan *chan)
> {
> + if (chan->local == NULL)
> + return;
> +
> WARN_ONCE(!device->device_release && chan->client_count,
> "%s called while %d clients hold a reference\n",
> __func__, chan->client_count);
next prev parent reply other threads:[~2023-12-13 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 16:04 [PATCH] dmaengine: fix NULL pointer in channel unregistration function Amelie Delaunay
2023-12-13 16:55 ` Dave Jiang [this message]
2023-12-21 16:30 ` 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=be59d5ac-fabb-4a05-99d4-fb281f7ea507@intel.com \
--to=dave.jiang@intel.com \
--cc=amelie.delaunay@foss.st.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.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