linux-kernel - Re: [PATCH v2 RESEND] dmaengine: tegra186: Fix residual calculation

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: <171161158127.113367.3353184486729352623.b4-ty@kernel.org>
Date: Thu, 28 Mar 2024 13:09:41 +0530
From: Vinod Koul <vkoul@...nel.org>
To: ldewangan@...dia.com, jonathanh@...dia.com, thierry.reding@...il.com, 
 dmaengine@...r.kernel.org, linux-tegra@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Akhil R <akhilrajeev@...dia.com>
Subject: Re: [PATCH v2 RESEND] dmaengine: tegra186: Fix residual
 calculation


On Fri, 15 Mar 2024 18:14:11 +0530, Akhil R wrote:
> The existing residual calculation returns an incorrect value when
> bytes_xfer == bytes_req. This scenario occurs particularly with drivers
> like UART where DMA is scheduled for maximum number of bytes and is
> terminated when the bytes inflow stops. At higher baud rates, it could
> request the tx_status while there is no bytes left to transfer. This will
> lead to incorrect residual being set. Hence return residual as '0' when
> bytes transferred equals to the bytes requested.
> 
> [...]

Applied, thanks!

[1/1] dmaengine: tegra186: Fix residual calculation
      commit: 30f0ced9971b2d8c8c24ae75786f9079489a012d

Best regards,
-- 
~Vinod