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,
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] ASoC: qcom: Fix NULL Dereference in asoc_qcom_lpass_cpu_platform_probe()
Date: Sat, 5 Oct 2024 17:40:53 +0200 [thread overview]
Message-ID: <ee94b16a-baa7-471c-997e-f1bf17b074b8@web.de> (raw)
In-Reply-To: <20241003152739.9650-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
> triggerred without addtional check.
…
* How do you think about to use the term “null pointer dereference”
for the final commit message (including the summary phrase)?
* Would you like to avoid any typos here?
…
> ---
> sound/soc/qcom/lpass-cpu.c | 2 ++
Did you overlook to add a version description behind the marker line?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc1#n723
Regards,
Markus
next prev parent reply other threads:[~2024-10-05 15:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 16:12 [PATCH] ASoC: qcom: Fix NULL Dereference in asoc_qcom_lpass_cpu_platform_probe() Gax-c
2024-10-03 5:54 ` Greg KH
2024-10-03 15:27 ` Gax-c
2024-10-05 15:40 ` Markus Elfring [this message]
2024-10-06 8:29 ` Greg Kroah-Hartman
2024-10-06 8:56 ` Markus Elfring
2024-10-06 10:08 ` Greg Kroah-Hartman
2024-10-06 11:12 ` Markus Elfring
2024-10-07 12:20 ` Markus Elfring
2024-10-06 20:23 ` [PATCH] " Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2024-10-01 21:02 Gax-c
2024-10-02 5:47 ` Krzysztof Kozlowski
2024-10-01 0:24 Gax-c
2024-10-01 19:45 ` Krzysztof Kozlowski
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=ee94b16a-baa7-471c-997e-f1bf17b074b8@web.de \
--to=markus.elfring@web.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chenyuan0y@gmail.com \
--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