In the Linux kernel, the following vulnerability has been resolved: dmaengine: fsl-edma: don't explicitly disable clocks in .remove() The clocks in fsledmaengine::muxclk are allocated and enabled with devmclkgetenabled(), which automatically cleans these resources up, but these clocks are also manually disabled in fsledmaremove(). This causes warnings on driver removal for each clock: edmamodule already disabled WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1200 clkcoredisable+0x198/0x1c8 [...] Call trace: clkcoredisable+0x198/0x1c8 (P) clkdisable+0x34/0x58 fsledmaremove+0x74/0xe8 [fsledma] [...] ---[ end trace 0000000000000000 ]--- edmamodule already unprepared WARNING: CPU: 0 PID: 418 at drivers/clk/clk.c:1059 clkcoreunprepare+0x1f8/0x220 [...] Call trace: clkcoreunprepare+0x1f8/0x220 (P) clkunprepare+0x34/0x58 fsledmaremove+0x7c/0xe8 [fsledma] [...] ---[ end trace 0000000000000000 ]--- Fix these warnings by removing the unnecessary fsldisableclocks() call in fsledma_remove().