drm/msm/gpu: Don't allow zero fence_id
authorRob Clark <robdclark@chromium.org>
Mon, 29 Nov 2021 18:23:44 +0000 (10:23 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 27 Jan 2022 10:03:32 +0000 (11:03 +0100)
commite5d61c5b9c9cc0f08fc7ca47f15153e35e3059f5
tree66f0d326a79d242f871de7c5fa4cf9ff67f00d23
parent89166801f80dc64083212eef1308bfc62f6844f1
drm/msm/gpu: Don't allow zero fence_id

[ Upstream commit ca3ffcbeb0c866d9b0cb38eaa2bd4416597b5966 ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/gpu/drm/msm/msm_gem_submit.c