From: Vinod Koul <vkoul@kernel.org>
To: peter.ujfalusi@gmail.com, Henry Martin <bsdhenrymartin@gmail.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dmaengine: ti: Add NULL check in udma_probe()
Date: Wed, 14 May 2025 16:03:08 +0100 [thread overview]
Message-ID: <174723498843.115803.15165946695069765623.b4-ty@kernel.org> (raw)
In-Reply-To: <20250402023900.43440-1-bsdhenrymartin@gmail.com>
On Wed, 02 Apr 2025 10:39:00 +0800, Henry Martin wrote:
> devm_kasprintf() returns NULL when memory allocation fails. Currently,
> udma_probe() does not check for this case, which results in a NULL
> pointer dereference.
>
> Add NULL check after devm_kasprintf() to prevent this issue.
>
>
> [...]
Applied, thanks!
[1/1] dmaengine: ti: Add NULL check in udma_probe()
commit: fd447415e74bccd7362f760d4ea727f8e1ebfe91
Best regards,
--
~Vinod
prev parent reply other threads:[~2025-05-14 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 2:39 [PATCH v1] dmaengine: ti: Add NULL check in udma_probe() Henry Martin
2025-04-17 21:51 ` Nathan Lynch
2025-04-24 3:10 ` henry martin
2025-05-01 10:37 ` Péter Ujfalusi
2025-05-14 15:03 ` Vinod Koul [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=174723498843.115803.15165946695069765623.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=bsdhenrymartin@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.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