linux-kernel - Re: [PATCH 3/5] sparc64/iommu: allow large DMA masks

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: <20190215.103458.2233581578201067146.davem@davemloft.net>
Date:   Fri, 15 Feb 2019 10:34:58 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     hch@....de
Cc:     deller@....de, robin.murphy@....com,
        iommu@...ts.linux-foundation.org, sparclinux@...r.kernel.org,
        linux-parisc@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5] sparc64/iommu: allow large DMA masks

From: Christoph Hellwig <hch@....de>
Date: Fri, 15 Feb 2019 15:45:57 +0100

> We've been moving to a model where the device just sets the DMA mask
> supported by it, instead of having to fallback to something it thinks
> the platform might support.  Sparc64 is the remaining holdout forcing
> drivers to supply a matching mask.  Change dma_4u_supported to just
> check if the supplied dma mask is large enough as nothing in the
> iommu.c code (or the core DMA code) actually looks at the DMA mask
> later on.
> 
> Signed-off-by: Christoph Hellwig <hch@....de>

Acked-by: David S. Miller <davem@...emloft.net>