[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <157678458608.6469.7303602517496484124@skylake-alporthouse-com>
Date: Thu, 19 Dec 2019 19:43:06 +0000
From: Chris Wilson <chris@...is-wilson.co.uk>
To: Colin King <colin.king@...onical.com>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
dri-devel@...ts.freedesktop.org, intel-gfx@...ts.freedesktop.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] drm/i915: fix uninitialized pointer reads on pointers to
and from
Quoting Colin King (2019-12-19 19:09:16)
> From: Colin Ian King <colin.king@...onical.com>
>
> Currently pointers to and from are not initialized and may contain
> garbage values. This will cause uninitialized pointer reads in the
> call to intel_frontbuffer_track and later checks to see if to and from
> are null. Fix this by ensuring to and from are initialized to NULL.
>
> Addresses-Coverity: ("Uninitialised pointer read)"
> Fixes: da42104f589d ("drm/i915: Hold reference to intel_frontbuffer as we track activity")
> Signed-off-by: Colin Ian King <colin.king@...onical.com>
"D'oh"
Reviewed-by: Chris Wilson <chris@...is-wilson.co.uk>
-Chris
Powered by blists - more mailing lists