linux-kernel - Re: [PATCH] dra7: sata: Fix SATA with CONFIG_ARM

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200305151636.GA4870@lst.de>
Date:   Thu, 5 Mar 2020 16:16:36 +0100
From:   Christoph Hellwig <hch@....de>
To:     Robin Murphy <robin.murphy@....com>
Cc:     Roger Quadros <rogerq@...com>, Tony Lindgren <tony@...mide.com>,
        Christoph Hellwig <hch@....de>, yan-liu@...com,
        linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        "Nori, Sekhar" <nsekhar@...com>
Subject: Re: [PATCH] dra7: sata: Fix SATA with CONFIG_ARM_LPAE enabled

On Thu, Mar 05, 2020 at 12:30:56PM +0000, Robin Murphy wrote:
> Right - LPAE configs should be getting dma-direct ops since 5.3, which 
> already respect the limit. For non-LPAE configs it means you go from being 
> broken from having no limit at all, to having a limit set but not 
> respected, which is still equally broken, but no *more* so than before.

Actually, dma-direct doesn't automatically respect the bus limit.  For
various architectures including arm it uses the arch_dma_alloc callout,
which for arm just uses the existing arm coherent allocator.

Thay being said I'm still looking for reviewers for the arm dma coherent
allocator bus limit fix..