In the Linux kernel, the following vulnerability has been resolved: dmaengine: fsl-edma: don't...

In the Linux kernel, the following vulnerability has been resolved:

dmaengine: fsl-edma: don't explicitly disable clocks in .remove()

The clocks in fsl_edma_engine::muxclk are allocated and enabled with devm_clk_get_enabled(), which automatically cleans these resources up, but these clocks are also manually disabled in fsl_edma_remove(). This causes warnings on driver removal for each clock:

    edma_module already disabled
    WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1200 clk_core_disable+0x198/0x1c8
    [...]
    Call trace:
     clk_core_disable+0x198/0x1c8 (P)
     clk_disable+0x34/0x58
     fsl_edma_remove+0x74/0xe8 [fsl_edma]
     [...]
    ---[ end trace 0000000000000000 ]---
    edma_module already unprepared
    WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1059 clk_core_unprepare+0x1f8/0x220
    [...]
    Call trace:
     clk_core_unprepare+0x1f8/0x220 (P)
     clk_unprepare+0x34/0x58
     fsl_edma_remove+0x7c/0xe8 [fsl_edma]
     [...]
    ---[ end trace 0000000000000000 ]---

Fix these warnings by removing the unnecessary fsl_disable_clocks() call in fsl_edma_remove().