dma-buf: fix check in dma_resv_add_fence
authorChristian König <christian.koenig@amd.com>
Tue, 14 Nov 2023 12:37:09 +0000 (13:37 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 8 Dec 2023 07:51:15 +0000 (08:51 +0100)
commitfc98ea2699c090e0377d16d733dca7a0b7508237
treeb3ef6d80fd4c0d1c64dd83eb727f9a9e2d78259d
parent4da1556996fa510dcc7787e21f5f42491c369b19
dma-buf: fix check in dma_resv_add_fence

commit 95ba893c9f4feb836ddce627efd0bb6af6667031 upstream.

It's valid to add the same fence multiple times to a dma-resv object and
we shouldn't need one extra slot for each.

Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Fixes: a3f7c10a269d5 ("dma-buf/dma-resv: check if the new fence is really later")
Cc: stable@vger.kernel.org # v5.19+
Link: https://patchwork.freedesktop.org/patch/msgid/20231115093035.1889-1-christian.koenig@amd.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/dma-buf/dma-resv.c
include/linux/dma-fence.h