linux-kernel - Re: [PATCH v6 0/5] vfio: handle DMA map/unmap up to the addressable limit

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

Message-ID: <aQ6Qmrzf7X0EP9aJ@devgpu015.cco6.facebook.com>
Date: Fri, 7 Nov 2025 16:36:42 -0800
From: Alex Mastro <amastro@...com>
To: David Matlack <dmatlack@...gle.com>
CC: Alex Williamson <alex@...zbot.org>, Jason Gunthorpe <jgg@...pe.ca>,
        Alejandro Jimenez <alejandro.j.jimenez@...cle.com>,
        <kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 0/5] vfio: handle DMA map/unmap up to the addressable
 limit

On Fri, Nov 07, 2025 at 10:24:27PM +0000, David Matlack wrote:
> On 2025-11-07 12:44 AM, David Matlack wrote:
> > On 2025-10-28 09:14 AM, Alex Mastro wrote:
> For type1, I tracked down -EINVAL as coming from
> vfio_iommu_iova_dma_valid() returning false.
> 
> The system I tested on only supports IOVAs up through
> 0x00ffffffffffffff.
> 
> Do you know what systems supports up to 0xffffffffffffffff? I would like
> to try to make sure I am getting test coverage there when running these
> tests.

I observed this on an AMD EPYC 9654 server.

> In the meantime, I sent out a fix to skip this test instead of failing:
> 
>   https://lore.kernel.org/kvm/20251107222058.2009244-1-dmatlack@google.com/

Thanks for the fix -- acked. My tests were making too strong an assumption
about availability of those ranges.

Alex