From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Shanker Donthineni <sdonthineni@nvidia.com>,
Maxime Ripard <mripard@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
"T . J . Mercier" <tjmercier@google.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma: contiguous: Check return value of dma_contiguous_reserve_area()
Date: Mon, 2 Feb 2026 16:52:33 +0100 [thread overview]
Message-ID: <6e57194b-3cb0-4593-af9f-075f1807dd6a@samsung.com> (raw)
In-Reply-To: <20260129181317.2429196-1-sdonthineni@nvidia.com>
On 29.01.2026 19:13, Shanker Donthineni wrote:
> Commit 8f1fc1bf1a3d ("dma: contiguous: Reserve default CMA heap")
> introduced a bug where dma_heap_cma_register_heap() is called with
> a NULL pointer when dma_contiguous_reserve_area() fails to reserve
> the CMA area.
>
> When dma_contiguous_reserve_area() fails, dma_contiguous_default_area
> remains NULL (initialized as a global variable), but the code doesn't
> check the return value and proceeds to call dma_heap_cma_register_heap()
> with this NULL pointer.
>
> Later during boot, add_cma_heaps() iterates through the dma_areas[]
> array and attempts to register heaps. When it encounters the NULL
> pointer stored by the earlier call, it crashes in __add_cma_heap()
> -> dma_heap_add() when trying to dereference the NULL CMA pointer.
>
> The crash manifests as:
> Unable to handle kernel NULL pointer dereference at virtual address
> 0000000000000038
> ...
> Call trace:
> dma_heap_add+0x40/0x2b0
> __add_cma_heap+0x80/0xe0
> add_cma_heaps+0x64/0xb0
> do_one_initcall+0x60/0x318
> kernel_init_freeable+0x260/0x2f0
> kernel_init+0x2c/0x168
> ret_from_fork+0x10/0x20
>
> Fix this by checking the return value of dma_contiguous_reserve_area()
> and only calling dma_heap_cma_register_heap() when the reservation
> succeeds.
>
> Fixes: 8f1fc1bf1a3d ("dma: contiguous: Reserve default CMA heap")
> Signed-off-by: Shanker Donthineni <sdonthineni@nvidia.com>
Applied to dma-mapping-fixes, thanks!
> ---
> kernel/dma/contiguous.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/dma/contiguous.c b/kernel/dma/contiguous.c
> index d8fd6f779f797..92c539d76412b 100644
> --- a/kernel/dma/contiguous.c
> +++ b/kernel/dma/contiguous.c
> @@ -247,10 +247,12 @@ void __init dma_contiguous_reserve(phys_addr_t limit)
> pr_debug("%s: reserving %ld MiB for global area\n", __func__,
> (unsigned long)selected_size / SZ_1M);
>
> - dma_contiguous_reserve_area(selected_size, selected_base,
> - selected_limit,
> - &dma_contiguous_default_area,
> - fixed);
> + ret = dma_contiguous_reserve_area(selected_size, selected_base,
> + selected_limit,
> + &dma_contiguous_default_area,
> + fixed);
> + if (ret)
> + return;
>
> ret = dma_heap_cma_register_heap(dma_contiguous_default_area);
> if (ret)
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
prev parent reply other threads:[~2026-02-02 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260129181410eucas1p2860c5d8fe66dfcaa98b29d5fa1f0b623@eucas1p2.samsung.com>
2026-01-29 18:13 ` Shanker Donthineni
2026-01-29 18:43 ` T.J. Mercier
2026-02-02 15:52 ` Marek Szyprowski [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=6e57194b-3cb0-4593-af9f-075f1807dd6a@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sdonthineni@nvidia.com \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.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®