From: Markus Elfring <Markus.Elfring@web.de>
To: Karan Sanghavi <karansanghvi98@gmail.com>,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Alexandre Mergnat <amergnat@baylibre.com>,
Angelo Gioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Chun-Kuang Hu <chunkuang.hu@kernel.org>,
David Airlie <airlied@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Shuah Khan <skhan@linuxfoundation.org>,
Simona Vetter <simona@ffwll.ch>,
Sui Jingfeng <sui.jingfeng@linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>, "CK Hu (胡俊光)" <ck.hu@mediatek.com>
Subject: Re: [PATCH] drm/mediatek: Initialize pointer before use to avoid undefiend behaviour
Date: Tue, 24 Dec 2024 17:09:54 +0100 [thread overview]
Message-ID: <8a5bdda5-5e2a-4b73-91a5-849b6060e7df@web.de> (raw)
In-Reply-To: <20241111-uninitializedpointer1601557-v1-1-7d03668e8141@gmail.com>
> Initialize the pointer with NULL as mtk_drm_of_get_ddp_ep_cid
> function might return before assigning value to next pointer
> but yet further dereference to next can lead to some undefined
> behavior as it may point to some invalid location.
* You may occasionally put more than 62 characters into text lines
of such a change description.
* Please avoid a typo the summary phrase.
…
> ---
> Coverity Message:
> CID 1601557: (#1 of 1): Uninitialized pointer read (UNINIT)
> 3. uninit_use: Using uninitialized value next.
May such information become a part for the final change description?
Regards,
Markus
next prev parent reply other threads:[~2024-12-24 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 18:14 Karan Sanghavi
2024-12-24 8:34 ` CK Hu (胡俊光)
2024-12-24 16:09 ` Markus Elfring [this message]
2024-12-27 9:51 ` Karan Sanghavi
2024-12-27 10:24 ` Markus Elfring
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=8a5bdda5-5e2a-4b73-91a5-849b6060e7df@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karansanghvi98@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=sui.jingfeng@linux.dev \
/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®