From: Alex Mastro <amastro@fb.com>
To: kernel test robot <lkp@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
<oe-kbuild-all@lists.linux.dev>, Jason Gunthorpe <jgg@ziepe.ca>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] vfio/type1: handle DMA map/unmap up to the addressable limit
Date: Sat, 11 Oct 2025 11:15:48 -0700 [thread overview]
Message-ID: <aOqe1JMVG5bg/iwU@devgpu015.cco6.facebook.com> (raw)
In-Reply-To: <202510111953.naYvy8XB-lkp@intel.com>
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.
prev parent reply other threads:[~2025-10-11 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 7:38 [PATCH v3 0/3] vfio: handle DMA map/unmap up to the addressable limit Alex Mastro
2025-10-10 7:38 ` [PATCH v3 1/3] vfio/type1: sanitize for overflow using check_*_overflow Alex Mastro
2025-10-10 7:38 ` [PATCH v3 2/3] vfio/type1: move iova increment to unmap_unpin_* caller Alex Mastro
2025-10-10 7:38 ` [PATCH v3 3/3] vfio/type1: handle DMA map/unmap up to the addressable limit Alex Mastro
2025-10-11 11:57 ` kernel test robot
2025-10-11 18:15 ` Alex Mastro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aOqe1JMVG5bg/iwU@devgpu015.cco6.facebook.com \
--to=amastro@fb.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox