[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb14ae3b-7a4f-4802-b9a7-9ffec3b951f9@web.de>
Date: Thu, 27 Jun 2024 13:33:40 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Ma Ke <make24@...as.ac.cn>, dri-devel@...ts.freedesktop.org,
Daniel Vetter <daniel@...ll.ch>, Dave Airlie <airlied@...hat.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Patrik Jakobsson <patrik.r.jakobsson@...il.com>,
Thomas Zimmermann <tzimmermann@...e.de>
Cc: stable@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
David Airlie <airlied@...il.com>
Subject: Re: [PATCH v2] drm/gma500: fix null pointer dereference in
cdv_intel_lvds_get_modes
> In cdv_intel_lvds_get_modes(), the return value of drm_mode_duplicate()
> is assigned to mode, which will lead to a NULL pointer dereference on
> failure of drm_mode_duplicate(). Add a check to avoid npd.
A) Can a wording approach (like the following) be a better change description?
A null pointer is stored in the local variable “mode” after a call
of the function “drm_mode_duplicate” failed. This pointer was passed to
a subsequent call of the function “drm_mode_probed_add” where an undesirable
dereference will be performed then.
Thus add a corresponding return value check.
B) Would you like to append parentheses to the function name
in the summary phrase?
C) How do you think about to put similar results from static source code
analyses into corresponding patch series?
Regards,
Markus
Powered by blists - more mailing lists