dma-buf/dma-resv: Respect num_fences when initializing the shared fence list.
authorMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
Tue, 24 Nov 2020 11:57:07 +0000 (12:57 +0100)
committerMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
Wed, 25 Nov 2020 09:48:28 +0000 (10:48 +0100)
We hardcode the maximum number of shared fences to 4, instead of
respecting num_fences. Use a minimum of 4, but more if num_fences
is higher.

This seems to have been an oversight when first implementing the
api.

Fixes: 04a5faa8cbe5 ("reservation: update api and add some helpers")
Cc: <stable@vger.kernel.org> # v3.17+
Reported-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20201124115707.406917-1-maarten.lankhorst@linux.intel.com
drivers/dma-buf/dma-resv.c

index bb5a42b10c2900629398e3ac4a33eff657feb472..6ddbeb5dfbf65aed3afe9b38f94e1e9149ebf5ba 100644 (file)
@@ -200,7 +200,7 @@ int dma_resv_reserve_shared(struct dma_resv *obj, unsigned int num_fences)
                        max = max(old->shared_count + num_fences,
                                  old->shared_max * 2);
        } else {
-               max = 4;
+               max = max(4ul, roundup_pow_of_two(num_fences));
        }
 
        new = dma_resv_list_alloc(max);