From: Jacob Pan <jacob.pan@linux.microsoft.com>
To: linux-kernel@vger.kernel.org,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Alex Williamson <alex.williamson@redhat.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
Jacob Pan <jacob.pan@linux.microsoft.com>
Cc: Zhang Yu <zhangyu1@microsoft.com>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>
Subject: Re: [PATCH v3 1/2] vfio: Fix unbalanced vfio_df_close call in no-iommu mode
Date: Thu, 10 Jul 2025 11:40:25 -0700 [thread overview]
Message-ID: <20250710114025.513b0af4@DESKTOP-0403QTC.> (raw)
In-Reply-To: <20250618234618.1910456-1-jacob.pan@linux.microsoft.com>
Hi Alex et al,
Just wondering if there are more comments?
Thanks,
Jacob
On Wed, 18 Jun 2025 16:46:17 -0700
Jacob Pan <jacob.pan@linux.microsoft.com> wrote:
> For devices with no-iommu enabled in IOMMUFD VFIO compat mode, the
> group open path skips vfio_df_open(), leaving open_count at 0. This
> causes a warning in vfio_assert_device_open(device) when
> vfio_df_close() is called during group close.
>
> The correct behavior is to skip only the IOMMUFD bind in the device
> open path for no-iommu devices. Commit 6086efe73498 omitted
> vfio_df_open(), which was too broad. This patch restores the previous
> behavior, ensuring the vfio_df_open is called in the group open path.
>
> Fixes: 6086efe73498 ("vfio-iommufd: Move noiommu compat validation
> out of vfio_iommufd_bind()") Suggested-by: Alex Williamson
> <alex.williamson@redhat.com> Suggested-by: Jason Gunthorpe
> <jgg@nvidia.com> Signed-off-by: Jacob Pan
> <jacob.pan@linux.microsoft.com> ---
> v3: Apply a concise fix from Alex
> v2: Use a fix from Jason
> ---
> drivers/vfio/group.c | 7 +++----
> drivers/vfio/iommufd.c | 4 ++++
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/vfio/group.c b/drivers/vfio/group.c
> index c321d442f0da..c376a6279de0 100644
> --- a/drivers/vfio/group.c
> +++ b/drivers/vfio/group.c
> @@ -192,11 +192,10 @@ static int vfio_df_group_open(struct
> vfio_device_file *df)
> * implies they expected translation to exist
> */
> if (!capable(CAP_SYS_RAWIO) ||
> - vfio_iommufd_device_has_compat_ioas(device,
> df->iommufd))
> + vfio_iommufd_device_has_compat_ioas(device,
> df->iommufd)) { ret = -EPERM;
> - else
> - ret = 0;
> - goto out_put_kvm;
> + goto out_put_kvm;
> + }
> }
>
> ret = vfio_df_open(df);
> diff --git a/drivers/vfio/iommufd.c b/drivers/vfio/iommufd.c
> index c8c3a2d53f86..a38d262c6028 100644
> --- a/drivers/vfio/iommufd.c
> +++ b/drivers/vfio/iommufd.c
> @@ -25,6 +25,10 @@ int vfio_df_iommufd_bind(struct vfio_device_file
> *df)
> lockdep_assert_held(&vdev->dev_set->lock);
>
> + /* Returns 0 to permit device opening under noiommu mode */
> + if (vfio_device_is_noiommu(vdev))
> + return 0;
> +
> return vdev->ops->bind_iommufd(vdev, ictx, &df->devid);
> }
>
next prev parent reply other threads:[~2025-07-10 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 23:46 Jacob Pan
2025-06-18 23:46 ` [PATCH v3 2/2] vfio: Prevent open_count decrement to negative Jacob Pan
2025-06-19 18:59 ` [PATCH v3 1/2] vfio: Fix unbalanced vfio_df_close call in no-iommu mode Jason Gunthorpe
2025-07-10 18:40 ` Jacob Pan [this message]
[not found] ` <76681.125071014402700656@us-mta-395.us.mimecast.lan>
2025-07-11 22:50 ` Alex Williamson
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=20250710114025.513b0af4@DESKTOP-0403QTC. \
--to=jacob.pan@linux.microsoft.com \
--cc=alex.williamson@redhat.com \
--cc=eahariha@linux.microsoft.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=yi.l.liu@intel.com \
--cc=zhangyu1@microsoft.com \
/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®