virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: baolu.lu@linux.intel.com, Kevin Tian <kevin.tian@intel.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Jean-Philippe Brucker <jean-philippe@linaro.org>,
	Nicolin Chen <nicolinc@nvidia.com>, Yi Liu <yi.l.liu@intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Joel Granados <j.granados@samsung.com>,
	iommu@lists.linux.dev, virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 08/10] iommufd: Associate fault object with iommufd_hw_pgtable
Date: Mon, 1 Jul 2024 13:26:05 +0800	[thread overview]
Message-ID: <8f57eb6c-d1da-4638-9b3e-a159dbed9624@linux.intel.com> (raw)
In-Reply-To: <Zn81gdjwJBfjXekJ@ziepe.ca>

On 2024/6/29 6:13, Jason Gunthorpe wrote:
> On Sun, Jun 16, 2024 at 02:11:53PM +0800, Lu Baolu wrote:
> 
>> @@ -308,13 +315,29 @@ int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd)
>>   		goto out_put_pt;
>>   	}
>>   
>> +	if (cmd->flags & IOMMU_HWPT_FAULT_ID_VALID) {
>> +		struct iommufd_fault *fault;
>> +
>> +		fault = iommufd_get_fault(ucmd, cmd->fault_id);
>> +		if (IS_ERR(fault)) {
>> +			rc = PTR_ERR(fault);
>> +			goto out_hwpt;
>> +		}
>> +		hwpt->fault = fault;
>> +		hwpt->domain->iopf_handler = iommufd_fault_iopf_handler;
>> +		hwpt->domain->fault_data = hwpt;
> 
> This is not the right refcounting for a longterm reference... The PT
> above shows the pattern:
> 
> 	pt_obj = iommufd_get_object(ucmd->ictx, cmd->pt_id, IOMMUFD_OBJ_ANY);
> 	hwpt_paging = iommufd_hwpt_paging_alloc()
>              	refcount_inc(&ioas->obj.users);
> 
> 	iommufd_put_object(ucmd->ictx, pt_obj);
> 
> Which is to say you need to incr users and then do the put object. And
> iommufd_object_abort_and_destroy() will always destroy the ref on the
> fault if the fault is non-null so the error handling will double free.
> 
> fail_nth is intended to catch this, but you have to add enough inputs
> to cover the new cases when you add them, it seems like that is
> missing in this series. ie add a fault object and hwpt alloc to a
> fail_nth test and see we execute the iommufd_ucmd_respond() failure
> path.

Yes. I will add below fail_nth case:

--- a/tools/testing/selftests/iommu/iommufd_utils.h
+++ b/tools/testing/selftests/iommu/iommufd_utils.h
@@ -201,6 +201,12 @@ static int _test_cmd_hwpt_alloc(int fd, __u32 
device_id, __u32 pt_id, __u32 ft_i
         ASSERT_EQ(0, _test_cmd_hwpt_alloc(self->fd, device_id, pt_id, 
fault_id, \
                                           flags, hwpt_id, data_type, 
data,      \
                                           data_len))
+#define test_err_hwpt_alloc_iopf(_errno, device_id, pt_id, fault_id, 
flags,     \
+                                hwpt_id, data_type, data, data_len) 
        \
+       EXPECT_ERRNO(_errno, 
        \
+                    _test_cmd_hwpt_alloc(self->fd, device_id, pt_id, 
fault_id, \
+                                         flags, hwpt_id, data_type, 
data,      \
+                                         data_len))

  #define test_cmd_hwpt_check_iotlb(hwpt_id, iotlb_id, expected) 
         \
         ({ 
        \
diff --git a/tools/testing/selftests/iommu/iommufd.c 
b/tools/testing/selftests/iommu/iommufd.c
index 5b0169875a4d..93634e53e95e 100644
--- a/tools/testing/selftests/iommu/iommufd.c
+++ b/tools/testing/selftests/iommu/iommufd.c
@@ -338,6 +338,10 @@ TEST_F(iommufd_ioas, alloc_hwpt_nested)
                                            &nested_hwpt_id[1],
                                            IOMMU_HWPT_DATA_SELFTEST, &data,
                                            sizeof(data));
+               test_err_hwpt_alloc_iopf(ENOENT, self->device_id, 
parent_hwpt_id,
+                                        UINT32_MAX, 
IOMMU_HWPT_FAULT_ID_VALID,
+                                        &iopf_hwpt_id, 
IOMMU_HWPT_DATA_SELFTEST,
+                                        &data, sizeof(data));
                 test_cmd_hwpt_alloc_iopf(self->device_id, 
parent_hwpt_id, fault_id,
                                          IOMMU_HWPT_FAULT_ID_VALID, 
&iopf_hwpt_id,
                                          IOMMU_HWPT_DATA_SELFTEST, &data,

> 
> --- a/drivers/iommu/iommufd/hw_pagetable.c
> +++ b/drivers/iommu/iommufd/hw_pagetable.c
> @@ -14,7 +14,7 @@ static void __iommufd_hwpt_destroy(struct iommufd_hw_pagetable *hwpt)
>                  iommu_domain_free(hwpt->domain);
>   
>          if (hwpt->fault)
> -               iommufd_put_object(hwpt->fault->ictx, &hwpt->fault->obj);
> +               refcount_dec(&hwpt->fault->obj.users);
>   }
>   
>   void iommufd_hwpt_paging_destroy(struct iommufd_object *obj)
> @@ -326,18 +326,17 @@ int iommufd_hwpt_alloc(struct iommufd_ucmd *ucmd)
>                  hwpt->fault = fault;
>                  hwpt->domain->iopf_handler = iommufd_fault_iopf_handler;
>                  hwpt->domain->fault_data = hwpt;
> +               refcount_inc(&fault->obj.users);
> +               iommufd_put_object(ucmd->ictx, &fault->obj);
>          }
>   
>          cmd->out_hwpt_id = hwpt->obj.id;
>          rc = iommufd_ucmd_respond(ucmd, sizeof(*cmd));
>          if (rc)
> -               goto out_put_fault;
> +               goto out_hwpt;
>          iommufd_object_finalize(ucmd->ictx, &hwpt->obj);
>          goto out_unlock;
>   
> -out_put_fault:
> -       if (cmd->flags & IOMMU_HWPT_FAULT_ID_VALID)
> -               iommufd_put_object(ucmd->ictx, &hwpt->fault->obj);
>   out_hwpt:
>          iommufd_object_abort_and_destroy(ucmd->ictx, &hwpt->obj);
>   out_unlock:
> 

.. and merge above change to this patch.

Best regards,
baolu

  reply	other threads:[~2024-07-01  5:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16  6:11 [PATCH v7 00/10] IOMMUFD: Deliver IO page faults to user space Lu Baolu
2024-06-16  6:11 ` [PATCH v7 01/10] iommu: Introduce domain attachment handle Lu Baolu
2024-06-28 20:46   ` Jason Gunthorpe
2024-06-16  6:11 ` [PATCH v7 02/10] iommu: Remove sva handle list Lu Baolu
2024-06-28 21:15   ` Jason Gunthorpe
2024-06-16  6:11 ` [PATCH v7 03/10] iommu: Add attach handle to struct iopf_group Lu Baolu
2024-06-17  7:41   ` Tian, Kevin
2024-06-18  1:35     ` Baolu Lu
2024-06-28 20:48   ` Jason Gunthorpe
2024-06-16  6:11 ` [PATCH v7 04/10] iommu: Extend domain attach group with handle support Lu Baolu
2024-06-28 21:06   ` Jason Gunthorpe
2024-06-29  3:58     ` Baolu Lu
2024-06-16  6:11 ` [PATCH v7 05/10] iommufd: Add fault and response message definitions Lu Baolu
2024-06-16  6:11 ` [PATCH v7 06/10] iommufd: Add iommufd fault object Lu Baolu
2024-06-28 22:14   ` Jason Gunthorpe
2024-06-16  6:11 ` [PATCH v7 07/10] iommufd: Fault-capable hwpt attach/detach/replace Lu Baolu
2024-06-28 21:17   ` Jason Gunthorpe
2024-07-01  5:55     ` Baolu Lu
2024-07-09 17:36       ` Jason Gunthorpe
2024-07-10  0:32         ` Tian, Kevin
2024-07-10  8:36         ` Baolu Lu
2024-06-16  6:11 ` [PATCH v7 08/10] iommufd: Associate fault object with iommufd_hw_pgtable Lu Baolu
2024-06-28 22:13   ` Jason Gunthorpe
2024-07-01  5:26     ` Baolu Lu [this message]
2024-06-16  6:11 ` [PATCH v7 09/10] iommufd/selftest: Add IOPF support for mock device Lu Baolu
2024-06-16  6:11 ` [PATCH v7 10/10] iommufd/selftest: Add coverage for IOPF test Lu Baolu
2024-06-17  7:46 ` [PATCH v7 00/10] IOMMUFD: Deliver IO page faults to user space Tian, Kevin
2024-06-28 22:14 ` Jason Gunthorpe
2024-07-02  6:42   ` Baolu Lu

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=8f57eb6c-d1da-4638-9b3e-a159dbed9624@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=j.granados@samsung.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=virtualization@lists.linux-foundation.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).