[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <af3a63a2-573b-2f72-501a-0bbc7c6a9686@canonical.com>
Date: Mon, 16 Nov 2020 11:28:24 +0000
From: Colin Ian King <colin.king@...onical.com>
To: Simon Ser <contact@...rsion.fr>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Sam Ravnborg <sam@...nborg.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][next] drm/atomic: avoid null pointer dereference on
pointer crtc
On 16/11/2020 11:08, Simon Ser wrote:
> On Monday, November 16, 2020 12:03 PM, Colin King <colin.king@...onical.com> wrote:
>
>> From: Colin Ian King colin.king@...onical.com
>>
>> Since moving to the new debug helper functions we now have a debug message
>> that dereferences crtc to print a kernel debug message when crtc is null
>> and so this debug message will now cause a null pointer dereference. Since
>> this is a debug message it probably is just simplest to fix this by just
>> removing the debug message altogether.
>
> NACK. This removes the log altogether instead of fixing it.
>
> A fix has already been pushed to drm-misc-next: 0003b687ee6d ("drm: fix
> oops in drm_atomic_set_crtc_for_connector").
>
Good to see this has already been fixed. Thanks.
Colin
Powered by blists - more mailing lists