Re: [PATCH] drm/amd: add the checking to avoid NULL pointer dereference

2018-11-22 Thread Christian König
Am 22.11.18 um 03:36 schrieb Sharma, Deepak: when returned fence is not valid mostly due to userspace ignored previous error causes NULL pointer dereference NAK, when the fence is NULL then this means it is already signaled and no longer in the container. In other words this is a normal case

RE: [PATCH] drm/amd: add the checking to avoid NULL pointer dereference

2018-11-21 Thread Zhou, David(ChunMing)
> -Original Message- > From: amd-gfx On Behalf Of > Sharma, Deepak > Sent: Thursday, November 22, 2018 10:37 AM > To: amd-gfx@lists.freedesktop.org > Cc: Sharma, Deepak > Subject: [PATCH] drm/amd: add the checking to avoid NULL pointer > dereference > > when returned fence is not valid