From: Markus Elfring <Markus.Elfring@web.de>
To: Zichen Xie <zichenxie0106@gmail.com>,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jaroslav Kysela <perex@perex.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Rohit kumar <quic_rohkumar@quicinc.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Takashi Iwai <tiwai@suse.com>
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Chenyuan Yang <chenyuan0y@gmail.com>,
Zijie Zhao <zzjas98@gmail.com>
Subject: Re: [PATCH v3] ASoC: qcom: Fix NULL Dereference in asoc_qcom_lpass_cpu_platform_probe()
Date: Mon, 7 Oct 2024 15:16:27 +0200 [thread overview]
Message-ID: <9be6b874-0c4d-4100-887f-0aa693985715@web.de> (raw)
In-Reply-To: <20241006205737.8829-1-zichenxie0106@gmail.com>
> A devm_kzalloc() in asoc_qcom_lpass_cpu_platform_probe() could
call?
> possibly return NULL pointer. NULL Pointer Dereference may be
Can the term “null pointer dereference” be applied for
the final commit message (including the summary phrase)?
> triggerred without addtional check.
triggered? additional?
Regards,
Markus
next parent reply other threads:[~2024-10-07 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241006205737.8829-1-zichenxie0106@gmail.com>
2024-10-07 13:16 ` Markus Elfring [this message]
2024-10-07 13:47 ` Mark Brown
2024-10-07 13:40 ` [v3?] " Markus Elfring
2024-10-07 14:14 ` Mark Brown
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=9be6b874-0c4d-4100-887f-0aa693985715@web.de \
--to=markus.elfring@web.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chenyuan0y@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_rohkumar@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=zichenxie0106@gmail.com \
--cc=zzjas98@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
all inboxes | Powered by JetHome®