linux-kernel - Re: [PATCH 2/5] dma-mapping: move the 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180911064802.GB6214@lst.de>
Date:   Tue, 11 Sep 2018 08:48:02 +0200
From:   Christoph Hellwig <hch@....de>
To:     Robin Murphy <robin.murphy@....com>
Cc:     Christoph Hellwig <hch@....de>, iommu@...ts.linux-foundation.org,
        Marek Szyprowski <m.szyprowski@...sung.com>,
        Paul Burton <paul.burton@...s.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] dma-mapping: move the dma_coherent flag to struct
 device

On Mon, Sep 10, 2018 at 05:06:40PM +0100, Robin Murphy wrote:
>>> Nits aside, this otherwise looks sane to me for factoring out the
>>> equivalent Xen and arm64 DMA ops cases.
>>
>> Like this? :)
>>
>> http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-maybe-coherent
>
> Man, that's going to take me a *lot* of time to pick through. All those 
> horrendous subtleties that I barely remember!

The good thing is that if I remember correctly there is just a single
patch that (intentionally) changes behavior.  The rest is just
refactoring and moving code around.

Anyway, I want to get this series in now, and the kick off the swiotlb
discussion with Konread.  We might not even get to the iommu patches
for this merge window depending on how long it takes.