linux-kernel - Re: [PATCH 03/12] MIPS/jazzdma: decouple from dma-direct

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

Message-ID: <20200911070730.GA22394@lst.de>
Date:   Fri, 11 Sep 2020 09:07:30 +0200
From:   Christoph Hellwig <hch@....de>
To:     Hillf Danton <hdanton@...a.com>
Cc:     Christoph Hellwig <hch@....de>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org
Subject: Re: [PATCH 03/12] MIPS/jazzdma: decouple from dma-direct

On Thu, Sep 10, 2020 at 10:12:33PM +0800, Hillf Danton wrote:
> 
> On Tue,  8 Sep 2020 18:47:49 +0200 Christoph Hellwig wrote:
> > 
> > The jazzdma ops implement support for a very basic IOMMU.  Thus we really
> > should not use the dma-direct code that takes physical address limits
> > into account.  This survived through the great MIPS DMA ops cleanup mostly
> > because I was lazy, but now it is time to fully split the implementations.
> 
> A minor change in behavior, do we need to clear the dma buf as the
> dma-direct code does?

Yes, I've fixed this up.