netdev - Re: [PATCH 3/4] net: qcom/emac: enforce DMA address restrictions

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: <20171012.095837.2057549694773237248.davem@davemloft.net>
Date:   Thu, 12 Oct 2017 09:58:37 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     timur@...eaurora.org
Cc:     David.Laight@...LAB.COM, netdev@...r.kernel.org
Subject: Re: [PATCH 3/4] net: qcom/emac: enforce DMA address restrictions

From: Timur Tabi <timur@...eaurora.org>
Date: Thu, 12 Oct 2017 09:13:25 -0500

> On 10/12/17 4:30 AM, David Laight wrote:
>> Isn't the memory allocated by a single kzalloc() call?
> 
> dma_alloc_coherenent, actually.
> 
>> IIRC that guarantees it doesn't cross a power or 2 boundary less than
>> the size.
> 
> I'm pretty sure that kzalloc does not make that guarantee, and I don't
> think dma_alloc_coherent does either.

Both make that guarantee, even when an IOMMU is used.