iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Eric Farman <farman@linux.ibm.com>
To: Nicolin Chen <nicolinc@nvidia.com>,
	jgg@nvidia.com, kevin.tian@intel.com, joro@8bytes.org,
	will@kernel.org, robin.murphy@arm.com,
	alex.williamson@redhat.com, shuah@kernel.org
Cc: yi.l.liu@intel.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux.dev, kvm@vger.kernel.org,
	linux-kselftest@vger.kernel.org, baolu.lu@linux.intel.com,
	Matthew Rosato <mjrosato@linux.ibm.com>
Subject: Re: [PATCH v2 03/10] iommufd: Create access in vfio_iommufd_emulated_bind()
Date: Thu, 09 Feb 2023 13:58:47 -0500	[thread overview]
Message-ID: <c5f5b03420367dc4280cc54c36dbe03fb34fffa0.camel@linux.ibm.com> (raw)
In-Reply-To: <6083ba9a3c1d92baf1f324d4748333d80d3de830.1675802050.git.nicolinc@nvidia.com>

On Tue, 2023-02-07 at 13:17 -0800, Nicolin Chen wrote:
...snip...
> diff --git a/drivers/vfio/iommufd.c b/drivers/vfio/iommufd.c
> index 026f81a87dd7..dc9feab73db7 100644
> --- a/drivers/vfio/iommufd.c
> +++ b/drivers/vfio/iommufd.c
> @@ -141,10 +141,19 @@ static const struct iommufd_access_ops
> vfio_user_ops = {
>  int vfio_iommufd_emulated_bind(struct vfio_device *vdev,
>                                struct iommufd_ctx *ictx, u32
> *out_device_id)
>  {
> +       struct iommufd_access *user;
> +
>         lockdep_assert_held(&vdev->dev_set->lock);
>  
> -       vdev->iommufd_ictx = ictx;
>         iommufd_ctx_get(ictx);
> +       user = iommufd_access_create(vdev->iommufd_ictx,
> &vfio_user_ops, vdev);
> +       if (IS_ERR(user)) {
> +               iommufd_ctx_put(vdev->iommufd_ictx);

Matthew noticed a vfio-ccw and -ap regression that blames this patch.

Probably both the iommufd_access_create() and iommufd_ctx_put() calls
want the ictx variable itself, instead of the (uninitialized) pointer
in the vfio_device. (At least that gets -ccw and -ap working again.)

Thanks,
Eric

> +               return PTR_ERR(user);
> +       }
> +       iommufd_access_set_ioas(user, 0);
> +       vdev->iommufd_access = user;
> +       vdev->iommufd_ictx = ictx;
>         return 0;
>  }
>  EXPORT_SYMBOL_GPL(vfio_iommufd_emulated_bind);


  parent reply	other threads:[~2023-02-09 18:59 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 21:17 [PATCH v2 00/10] Add IO page table replacement support Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 01/10] iommu: Move dev_iommu_ops() to private header Nicolin Chen
2023-02-09  2:49   ` Tian, Kevin
2023-02-07 21:17 ` [PATCH v2 02/10] iommu: Introduce a new iommu_group_replace_domain() API Nicolin Chen
2023-02-09  2:55   ` Tian, Kevin
2023-02-09 13:23     ` Jason Gunthorpe
2023-02-10  1:34       ` Tian, Kevin
2023-02-10 23:51   ` Alex Williamson
2023-02-11  0:44     ` Jason Gunthorpe
2023-02-13  2:24       ` Tian, Kevin
2023-02-13  8:34         ` Baolu Lu
2023-02-13 14:45         ` Jason Gunthorpe
2023-02-14  3:29           ` Tian, Kevin
2023-02-15  6:10   ` Tian, Kevin
2023-02-15 12:52     ` Jason Gunthorpe
2023-02-22  2:11       ` Tian, Kevin
2023-02-24  0:57         ` Jason Gunthorpe
2023-02-24  8:07           ` Tian, Kevin
2023-02-07 21:17 ` [PATCH v2 03/10] iommufd: Create access in vfio_iommufd_emulated_bind() Nicolin Chen
2023-02-09  2:56   ` Tian, Kevin
2023-02-09 16:15     ` Nicolin Chen
2023-02-09 18:58   ` Eric Farman [this message]
2023-02-09 19:54     ` Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 04/10] iommufd/selftest: Add IOMMU_TEST_OP_ACCESS_SET_IOAS coverage Nicolin Chen
2023-02-09  2:59   ` Tian, Kevin
2023-02-07 21:17 ` [PATCH v2 05/10] iommufd: Add replace support in iommufd_access_set_ioas() Nicolin Chen
2023-02-09  3:13   ` Tian, Kevin
2023-02-09 20:28     ` Nicolin Chen
2023-02-09 20:49       ` Jason Gunthorpe
2023-02-09 22:18         ` Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 06/10] iommufd/selftest: Add coverage for access->ioas replacement Nicolin Chen
2023-02-07 21:17 ` [PATCH v2 07/10] iommufd/device: Make hwpt_list list_add/del symmetric Nicolin Chen
2023-02-09  3:23   ` Tian, Kevin
2023-02-09 13:24     ` Jason Gunthorpe
2023-02-10  1:46       ` Tian, Kevin
2023-02-10 21:17         ` Jason Gunthorpe
2023-02-13  2:12           ` Tian, Kevin
2023-02-07 21:18 ` [PATCH v2 08/10] iommufd/device: Use iommu_group_replace_domain() Nicolin Chen
2023-02-08  8:08   ` Liu, Yi L
2023-02-09 20:55     ` Nicolin Chen
2023-02-08  8:12   ` Liu, Yi L
2023-02-09 20:56     ` Nicolin Chen
2023-02-09  4:00   ` Tian, Kevin
2023-02-09 21:13     ` Nicolin Chen
2023-02-10  0:01       ` Jason Gunthorpe
2023-02-10 20:50         ` Nicolin Chen
2023-02-10  2:11       ` Tian, Kevin
2023-02-11  0:10         ` Nicolin Chen
2023-02-13  2:34           ` Tian, Kevin
2023-02-13  7:48             ` Nicolin Chen
2023-02-13  8:27               ` Tian, Kevin
2023-02-13 14:49               ` Jason Gunthorpe
2023-02-14 10:54                 ` Nicolin Chen
2023-02-15  1:37                   ` Tian, Kevin
2023-02-15  1:58                     ` Nicolin Chen
2023-02-15  2:15                       ` Tian, Kevin
2023-02-15  7:15                         ` Nicolin Chen
2023-02-15  7:24                           ` Tian, Kevin
2023-02-15 12:51                           ` Jason Gunthorpe
2023-02-14 10:59         ` Nicolin Chen
2023-02-15  1:38           ` Tian, Kevin
2023-02-15  7:16             ` Nicolin Chen
2023-02-07 21:18 ` [PATCH v2 09/10] vfio: Support IO page table replacement Nicolin Chen
2023-02-09  4:06   ` Tian, Kevin
2023-02-07 21:18 ` [PATCH v2 10/10] vfio: Do not allow !ops->dma_unmap in vfio_pin/unpin_pages() Nicolin Chen
2023-02-09  4:10   ` Tian, Kevin
2023-02-09 13:26     ` Jason Gunthorpe
2023-02-09 16:19       ` Nicolin Chen
2023-02-09  2:50 ` [PATCH v2 00/10] Add IO page table replacement support Tian, Kevin
2023-02-09 16:13   ` Nicolin Chen
2023-02-10  1:34     ` Tian, Kevin

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=c5f5b03420367dc4280cc54c36dbe03fb34fffa0.camel@linux.ibm.com \
    --to=farman@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=shuah@kernel.org \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.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;
as well as URLs for NNTP newsgroup(s).