diff options
| author | Rob Clark <robdclark@chromium.org> | 2021-11-29 10:23:44 -0800 |
|---|---|---|
| committer | Rob Clark <robdclark@chromium.org> | 2021-12-07 14:34:18 -0800 |
| commit | ca3ffcbeb0c866d9b0cb38eaa2bd4416597b5966 (patch) | |
| tree | 81a684c9c6192c2d23e4ae69fe0aec07beacbe8d /drivers/gpu/drm/msm/msm_gem_submit.c | |
| parent | b9c8accbdd511cf68aeffd0bdc955ddaaba49c52 (diff) | |
| download | linux-ca3ffcbeb0c866d9b0cb38eaa2bd4416597b5966.tar.bz2 | |
drm/msm/gpu: Don't allow zero fence_id
Elsewhere we treat zero as "no fence" and __msm_gem_submit_destroy()
skips removal from fence_idr. We could alternately change this to use
negative values for "no fence" but I think it is more clear to not allow
zero as a valid fence_id.
Signed-off-by: Rob Clark <robdclark@chromium.org>
Fixes: a61acbbe9cf8 ("drm/msm: Track "seqno" fences by idr")
Link: https://lore.kernel.org/r/20211129182344.292609-1-robdclark@gmail.com
Signed-off-by: Rob Clark <robdclark@chromium.org>
Diffstat (limited to 'drivers/gpu/drm/msm/msm_gem_submit.c')
| -rw-r--r-- | drivers/gpu/drm/msm/msm_gem_submit.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/gpu/drm/msm/msm_gem_submit.c b/drivers/gpu/drm/msm/msm_gem_submit.c index 282628d6b72c..6cfa984dee6a 100644 --- a/drivers/gpu/drm/msm/msm_gem_submit.c +++ b/drivers/gpu/drm/msm/msm_gem_submit.c @@ -881,7 +881,7 @@ int msm_ioctl_gem_submit(struct drm_device *dev, void *data, * to the underlying fence. */ submit->fence_id = idr_alloc_cyclic(&queue->fence_idr, - submit->user_fence, 0, INT_MAX, GFP_KERNEL); + submit->user_fence, 1, INT_MAX, GFP_KERNEL); if (submit->fence_id < 0) { ret = submit->fence_id = 0; submit->fence_id = 0; |