diff options
author | Erik Kurzinger <ekurzinger@nvidia.com> | 2024-02-21 10:44:28 -0800 |
---|---|---|
committer | Simon Ser <contact@emersion.fr> | 2024-02-22 13:52:52 +0100 |
commit | 2aa6f5b0fd052e363bb9d4b547189f0bf6b3d6d3 (patch) | |
tree | 1f9e2e1c2acdfc5b2756e18f6b2ef0d711204115 /drivers/gpu/host1x/dev.c | |
parent | 3c43177ffb54ea5be97505eb8e2690e99ac96bc9 (diff) |
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
Diffstat (limited to 'drivers/gpu/host1x/dev.c')
0 files changed, 0 insertions, 0 deletions