[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8a5bdda5-5e2a-4b73-91a5-849b6060e7df@web.de>
Date: Tue, 24 Dec 2024 17:09:54 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Karan Sanghavi <karansanghvi98@...il.com>,
dri-devel@...ts.freedesktop.org, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
Alexandre Mergnat <amergnat@...libre.com>,
Angelo Gioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Chun-Kuang Hu <chunkuang.hu@...nel.org>, David Airlie <airlied@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Shuah Khan <skhan@...uxfoundation.org>, Simona Vetter <simona@...ll.ch>,
Sui Jingfeng <sui.jingfeng@...ux.dev>
Cc: LKML <linux-kernel@...r.kernel.org>, CK Hu (胡俊光)
<ck.hu@...iatek.com>
Subject: Re: [PATCH] drm/mediatek: Initialize pointer before use to avoid
undefiend behaviour
> 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
Powered by blists - more mailing lists