linux-kernel - Re: [PATCH RESEND] dmaengine: ti: k3-udma: Use cap_mask directly from dma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174490311144.238609.16715270633918698511.b4-ty@kernel.org>
Date: Thu, 17 Apr 2025 20:48:31 +0530
From: Vinod Koul <vkoul@...nel.org>
To: peter.ujfalusi@...il.com, grygorii.strashko@...com, 
 Yemike Abhilash Chandra <y-abhilashchandra@...com>
Cc: vaishnav.a@...com, u-kumar1@...com, dmaengine@...r.kernel.org, 
 linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH RESEND] dmaengine: ti: k3-udma: Use cap_mask directly
 from dma_device structure instead of a local copy


On Thu, 17 Apr 2025 13:25:21 +0530, Yemike Abhilash Chandra wrote:
> Currently, a local dma_cap_mask_t variable is used to store device
> cap_mask within udma_of_xlate(). However, the DMA_PRIVATE flag in
> the device cap_mask can get cleared when the last channel is released.
> This can happen right after storing the cap_mask locally in
> udma_of_xlate(), and subsequent dma_request_channel() can fail due to
> mismatch in the cap_mask. Fix this by removing the local dma_cap_mask_t
> variable and directly using the one from the dma_device structure.
> 
> [...]

Applied, thanks!

[1/1] dmaengine: ti: k3-udma: Use cap_mask directly from dma_device structure instead of a local copy
      commit: 8ca9590c39b69b55a8de63d2b21b0d44f523b43a

Best regards,
-- 
~Vinod