linux-kernel - Re: [PATCH v3 3/3] vfio/type1: 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: <aOqe1JMVG5bg/iwU@devgpu015.cco6.facebook.com>
Date: Sat, 11 Oct 2025 11:15:48 -0700
From: Alex Mastro <amastro@...com>
To: kernel test robot <lkp@...el.com>
CC: Alex Williamson <alex.williamson@...hat.com>,
        <oe-kbuild-all@...ts.linux.dev>, Jason Gunthorpe <jgg@...pe.ca>,
        Alejandro
 Jimenez <alejandro.j.jimenez@...cle.com>,
        <kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 3/3] vfio/type1: handle DMA map/unmap up to the
 addressable limit

On Sat, Oct 11, 2025 at 07:57:07PM +0800, kernel test robot wrote:
> >> include/linux/limits.h:25:25: warning: conversion from 'long long unsigned int' to 'dma_addr_t' {aka 'unsigned int'} changes value from '18446744073709551615' to '4294967295' [-Woverflow]
>       25 | #define U64_MAX         ((u64)~0ULL)
>          |                         ^
>    drivers/vfio/vfio_iommu_type1.c:1361:28: note: in expansion of macro 'U64_MAX'
>     1361 |                 iova_end = U64_MAX;
>          |                            ^~~~~~~

I see. I suppose it should be ~(dma_addr_t)0 . I don't see a DMA_ADDR_MAX.