dma-buf: fix timeout handling in dma_resv_wait_timeout v2
commit 2b95a7db6e0f75587bffddbb490399cbb87e4985 upstream. Even the kerneldoc says that with a zero timeout the function should not wait for anything, but still return 1 to indicate that the fences are signaled now. Unfortunately that isn't what was implemented, instead of only returning 1 we also waited for at least one jiffies. Fix that by adjusting the handling to what the function is actually documented to do. v2: improve code readability Reported-by: Marek Olšák <marek.olsak@amd.com> Reported-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Christian König <christian.koenig@amd.com> Reviewed-by: Lucas Stach <l.stach@pengutronix.de> Cc: <stable@vger.kernel.org> Link: https://lore.kernel.org/r/20250129105841.1806-1-christian.koenig@amd.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
59205a3e93
commit
d8eab407c0
@@ -678,11 +678,13 @@ long dma_resv_wait_timeout(struct dma_resv *obj, enum dma_resv_usage usage,
|
|||||||
dma_resv_iter_begin(&cursor, obj, usage);
|
dma_resv_iter_begin(&cursor, obj, usage);
|
||||||
dma_resv_for_each_fence_unlocked(&cursor, fence) {
|
dma_resv_for_each_fence_unlocked(&cursor, fence) {
|
||||||
|
|
||||||
ret = dma_fence_wait_timeout(fence, intr, ret);
|
ret = dma_fence_wait_timeout(fence, intr, timeout);
|
||||||
if (ret <= 0) {
|
if (ret <= 0)
|
||||||
dma_resv_iter_end(&cursor);
|
break;
|
||||||
return ret;
|
|
||||||
}
|
/* Even for zero timeout the return value is 1 */
|
||||||
|
if (timeout)
|
||||||
|
timeout = ret;
|
||||||
}
|
}
|
||||||
dma_resv_iter_end(&cursor);
|
dma_resv_iter_end(&cursor);
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user