[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174723495814.115648.10076437402947235700.b4-ty@kernel.org>
Date: Wed, 14 May 2025 16:02:38 +0100
From: Vinod Koul <vkoul@...nel.org>
To: sean.wang@...iatek.com, matthias.bgg@...il.com,
angelogioacchino.delregno@...labora.com,
Qiu-ji Chen <chenqiuji666@...il.com>
Cc: dmaengine@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
baijiaju1990@...il.com, stable@...r.kernel.org
Subject: Re: [PATCH v2] dmaengine: mediatek: Fix a possible deadlock error
in mtk_cqdma_tx_status()
On Thu, 08 May 2025 15:36:33 +0800, Qiu-ji Chen wrote:
> Fix a potential deadlock bug. Observe that in the mtk-cqdma.c
> file, functions like mtk_cqdma_issue_pending() and
> mtk_cqdma_free_active_desc() properly acquire the pc lock before the vc
> lock when handling pc and vc fields. However, mtk_cqdma_tx_status()
> violates this order by first acquiring the vc lock before invoking
> mtk_cqdma_find_active_desc(), which subsequently takes the pc lock. This
> reversed locking sequence (vc → pc) contradicts the established
> pc → vc order and creates deadlock risks.
>
> [...]
Applied, thanks!
[1/1] dmaengine: mediatek: Fix a possible deadlock error in mtk_cqdma_tx_status()
commit: 157ae5ffd76a2857ccb4b7ce40bc5a344ca00395
Best regards,
--
~Vinod
Powered by blists - more mailing lists