From: Alex Williamson <alex.williamson@redhat.com>
To: jianchunfu <jianchunfu@cmss.chinamobile.com>
Cc: cohuck@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers:vfio: make the logic cleaner with braket
Date: Tue, 8 Mar 2022 13:59:48 -0700 [thread overview]
Message-ID: <20220308135948.15ddd34c.alex.williamson@redhat.com> (raw)
In-Reply-To: <20220308094946.139059-1-jianchunfu@cmss.chinamobile.com>
On Tue, 8 Mar 2022 17:49:46 +0800
jianchunfu <jianchunfu@cmss.chinamobile.com> wrote:
> Use braket to avoid identifying operators in function
> vfio_iova_dirty_bitmap() and vfio_dma_do_unmap()
> when there are too many field values.
s/braket/bracket/ but we're actually adding parenthesis.
"to avoid identifying operators", to avoid confusing operators?
s/function/functions/ but this only lists two of the three.
How many are too many field values? Per this patch, apparently one?
These are not particularly confusing or unruly tests imo. Thanks,
Alex
> Signed-off-by: jianchunfu <jianchunfu@cmss.chinamobile.com>
> ---
> drivers/vfio/vfio_iommu_type1.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/vfio/vfio_iommu_type1.c b/drivers/vfio/vfio_iommu_type1.c
> index 9394aa944..199547012 100644
> --- a/drivers/vfio/vfio_iommu_type1.c
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -1251,7 +1251,7 @@ static int vfio_iova_dirty_bitmap(u64 __user *bitmap, struct vfio_iommu *iommu,
> return -EINVAL;
>
> dma = vfio_find_dma(iommu, iova + size - 1, 0);
> - if (dma && dma->iova + dma->size != iova + size)
> + if (dma && (dma->iova + dma->size) != (iova + size))
> return -EINVAL;
>
> for (n = rb_first(&iommu->dma_list); n; n = rb_next(n)) {
> @@ -1363,7 +1363,7 @@ static int vfio_dma_do_unmap(struct vfio_iommu *iommu,
> goto unlock;
>
> dma = vfio_find_dma(iommu, iova + size - 1, 0);
> - if (dma && dma->iova + dma->size != iova + size)
> + if (dma && (dma->iova + dma->size) != (iova + size))
> goto unlock;
> }
>
> @@ -2958,7 +2958,7 @@ static int vfio_iommu_type1_dirty_pages(struct vfio_iommu *iommu,
> ret = -EINVAL;
> goto out_unlock;
> }
> - if (!range.size || range.size & (iommu_pgsize - 1)) {
> + if (!range.size || (range.size & (iommu_pgsize - 1))) {
> ret = -EINVAL;
> goto out_unlock;
> }
prev parent reply other threads:[~2022-03-08 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 9:49 jianchunfu
2022-03-08 20:59 ` Alex Williamson [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=20220308135948.15ddd34c.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jianchunfu@cmss.chinamobile.com \
--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
all inboxes | Powered by JetHome®