linux-kernel - Re: use generic DMA mapping code in powerpc V4

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]

Date:   Thu, 13 Dec 2018 09:41:50 +0100
From:   Christian Zigotzky <chzigotzky@...osoft.de>
To:     Christoph Hellwig <hch@....de>
Cc:     linux-arch@...r.kernel.org,
        Darren Stevens <darren@...vens-zone.net>,
        linux-kernel@...r.kernel.org, Julian Margetson <runaway@...dw.ms>,
        linux-mm@...ck.org, iommu@...ts.linux-foundation.org,
        Paul Mackerras <paulus@...ba.org>,
        Olof Johansson <olof@...om.net>, linuxppc-dev@...ts.ozlabs.org
Subject: Re: use generic DMA mapping code in powerpc V4

On 12 December 2018 at 3:39PM, Christian Zigotzky wrote:
> Hi Christoph,
>
> Thanks a lot for your reply. I will test your patches tomorrow.
>
> Cheers,
> Christian
>
> Sent from my iPhone
>
>> On 12. Dec 2018, at 15:15, Christoph Hellwig <hch@....de> wrote:
>>
>> Thanks for bisecting.  I've spent some time going over the conversion
>> but can't really pinpoint it.  I have three little patches that switch
>> parts of the code to the generic version.  This is on top of the
>> last good commmit (977706f9755d2d697aa6f45b4f9f0e07516efeda).
>>
>> Can you check with whіch one things stop working?
>>
>>
>> <0001-get_required_mask.patch>
>> <0002-swiotlb-dma_supported.patch>
>> <0003-nommu-dma_supported.patch>
>> <0004-alloc-free.patch>

Today I tried the first patch (0001-get_required_mask.patch) with the 
last good commit (977706f9755d2d697aa6f45b4f9f0e07516efeda). 
Unfortunately this patch is already included in the last good commit 
(977706f9755d2d697aa6f45b4f9f0e07516efeda). I will try the next patch.

-- Christian