diff options
| author | Uwe Kleine-König <[email protected]> | 2022-07-21 22:40:54 +0200 |
|---|---|---|
| committer | Vinod Koul <[email protected]> | 2022-07-26 18:20:49 +0530 |
| commit | 1e42f82cbec7b2cc4873751e7791e6611901c5fc (patch) | |
| tree | 3bc5f1e6ba5d0851a079e96c5a101d800b62dd19 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 36834c67016794b8fa03d7672a5b7f2cc4529298 (diff) | |
dmaengine: sprd: Cleanup in .remove() after pm_runtime_get_sync() failed
It's not allowed to quit remove early without cleaning up completely.
Otherwise this results in resource leaks that probably yield graver
problems later. Here for example some tasklets might survive the lifetime
of the sprd-dma device and access sdev which is freed after .remove()
returns.
As none of the device freeing requires an active device, just ignore the
return value of pm_runtime_get_sync().
Signed-off-by: Uwe Kleine-König <[email protected]>
Reviewed-by: Baolin Wang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Vinod Koul <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions