diff options
| author | Ville Syrjälä <[email protected]> | 2023-07-13 22:47:45 +0300 |
|---|---|---|
| committer | Christian König <[email protected]> | 2023-07-15 13:57:30 +0200 |
| commit | 05abb3be91d8788328231ee02973ab3d47f5e3d2 (patch) | |
| tree | b78ac8554be1ca0505947ce1797b1d9d26df2041 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 73274c33d961f4aa0f968f763e2c9f4210b4f4a3 (diff) | |
dma-buf/dma-resv: Stop leaking on krealloc() failure
Currently dma_resv_get_fences() will leak the previously
allocated array if the fence iteration got restarted and
the krealloc_array() fails.
Free the old array by hand, and make sure we still clear
the returned *fences so the caller won't end up accessing
freed memory. Some (but not all) of the callers of
dma_resv_get_fences() seem to still trawl through the
array even when dma_resv_get_fences() failed. And let's
zero out *num_fences as well for good measure.
Cc: Sumit Semwal <[email protected]>
Cc: Christian König <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Fixes: d3c80698c9f5 ("dma-buf: use new iterator in dma_resv_get_fences v3")
Signed-off-by: Ville Syrjälä <[email protected]>
Reviewed-by: Christian König <[email protected]>
Cc: [email protected]
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Signed-off-by: Christian König <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions