drm/syncobj: handle NULL fence in syncobj_eventfd_entry_func
authorErik Kurzinger <ekurzinger@nvidia.com>
Wed, 21 Feb 2024 18:44:28 +0000 (10:44 -0800)
committerSimon Ser <contact@emersion.fr>
Thu, 22 Feb 2024 12:52:52 +0000 (13:52 +0100)
commit2aa6f5b0fd052e363bb9d4b547189f0bf6b3d6d3
tree1f9e2e1c2acdfc5b2756e18f6b2ef0d711204115
parent3c43177ffb54ea5be97505eb8e2690e99ac96bc9
drm/syncobj: handle NULL fence in syncobj_eventfd_entry_func

During syncobj_eventfd_entry_func, dma_fence_chain_find_seqno may set
the fence to NULL if the given seqno is signaled and a later seqno has
already been submitted. In that case, the eventfd should be signaled
immediately which currently does not happen.

This is a similar issue to the one addressed by commit b19926d4f3a6
("drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.").

As a fix, if the return value of dma_fence_chain_find_seqno indicates
success but it sets the fence to NULL, we will assign a stub fence to
ensure the following code still signals the eventfd.

v1 -> v2: assign a stub fence instead of signaling the eventfd

Signed-off-by: Erik Kurzinger <ekurzinger@nvidia.com>
Fixes: c7a472297169 ("drm/syncobj: add IOCTL to register an eventfd")
Signed-off-by: Simon Ser <contact@emersion.fr>
Link: https://patchwork.freedesktop.org/patch/msgid/20240221184527.37667-1-ekurzinger@nvidia.com
drivers/gpu/drm/drm_syncobj.c