linux-kernel - Re: [PATCH] dmaengine: Clarify cyclic transfer residue documentation

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]

Date:   Mon, 11 Apr 2022 19:16:02 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Paul Kocialkowski <paul.kocialkowski@...tlin.com>
Cc:     dmaengine@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
        Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH] dmaengine: Clarify cyclic transfer residue documentation

On 31-03-22, 15:41, Paul Kocialkowski wrote:
> The current documentation for the residue reported in a cyclic transfer
> case mentions that the reported residue should be relative to the current
> period only. However the definition of DMA_RESIDUE_GRANULARITY_SEGMENT
> specifies that the residue should be updated after each period for
> a cyclic transfer, which is in direct contradiction.
> 
> Moreover the pcm_dmaengine common code uses the residue relative to
> the whole cyclic buffer size, not one period.
> 
> Correct the residue-related documentation to reflect this.

Applied, thanks

-- 
~Vinod