From: Alex Mastro <amastro@fb.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
Jason Gunthorpe <jgg@ziepe.ca>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vfio: fix VFIO_IOMMU_UNMAP_DMA when end of range would overflow u64
Date: Tue, 7 Oct 2025 15:57:47 -0700 [thread overview]
Message-ID: <aOWa6yD0oyQSgFTW@devgpu015.cco6.facebook.com> (raw)
In-Reply-To: <20251007144328.186fc0d2.alex.williamson@redhat.com>
On Tue, Oct 07, 2025 at 02:43:28PM -0600, Alex Williamson wrote:
> I prefer this approach, thanks for tackling it. Consider splitting
> into a few patches for easier review, ex. discrete input sanitizing with
> proper overflow checking, refactoring the fast/slow handlers to
> increment iova in the caller, remainder to tie it all together. A few
> comments inline below.
Alright -- I'll try to stage incrementally. The proposed sequencing sgtm.
> > + u64 end, to_pin;
>
> end looks like a dma_addr_t and to_pin ought to be a size_t, right?
> Maybe iova_end and iova_size?
Yes, I think I've been sloppy with the types. Am too 64-bit oriented.
> > - if (!iommu || !pages)
> > + if (!iommu || !pages || npage < 0)
> > return -EINVAL;
> >
> > /* Supported for v2 version only */
> > if (!iommu->v2)
> > return -EACCES;
> >
> > + if (npage == 0)
> > + return 0;
> > +
> > + if (check_mul_overflow(npage, PAGE_SIZE, &to_pin))
> > + return -EINVAL;
> > +
> > + if (check_add_overflow(user_iova, to_pin - 1, &end))
> > + return -EINVAL;
> > +
>
> Why not the same checks on vfio_iommu_type1_unpin_pages()?
Will see if there's opportunity to stay more consistent.
> > if (WARN_ON(!phys)) {
> > - iova += PAGE_SIZE;
> > + pos += PAGE_SIZE;
> > continue;
> > }
> >
> > +
>
> Extra white space
Ack.
> > size = PAGE_SIZE;
> > p = phys + size;
> > i = iova + size;
> > - while (i < dma->iova + dma->size &&
> > + while (size + pos < dma->size &&
> > p == iommu_iova_to_phys(d->domain, i)) {
> > size += PAGE_SIZE;
> > p += PAGE_SIZE;
>
> I think the else branch after this has some use cases too, (iova -
> dma->iova) just becomes 'pos' in calculating vaddr, 'n' should be
> calculated as (dma->size - pos).
Missed this simplification - thanks.
> > + u64 end;
>
> Seems like a dma_addr_t. range_end? Thanks,
Ack
next prev parent reply other threads:[~2025-10-07 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 3:38 [PATCH] vfio: fix VFIO_IOMMU_UNMAP_DMA when end of range would overflow u64 Alex Mastro
2025-10-06 12:16 ` Jason Gunthorpe
2025-10-06 16:29 ` Alex Mastro
2025-10-06 22:50 ` Jason Gunthorpe
2025-10-07 0:39 ` Alex Mastro
2025-10-07 1:23 ` Alejandro Jimenez
2025-10-07 4:24 ` Alex Mastro
2025-10-07 14:41 ` Alejandro Jimenez
2025-10-07 20:43 ` Alex Williamson
2025-10-07 22:57 ` Alex Mastro [this message]
2025-10-07 11:48 ` Jason Gunthorpe
2025-10-07 14:46 ` Alejandro Jimenez
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=aOWa6yD0oyQSgFTW@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 \
/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