From: Karol Wachowski <karol.wachowski@linux.intel.com>
To: Maciej Falkowski <maciej.falkowski@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
lizhi.hou@amd.com,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Subject: Re: [PATCH] accel/ivpu: Fix page fault in ivpu_bo_unbind_all_bos_from_context()
Date: Wed, 1 Oct 2025 10:03:05 +0200 [thread overview]
Message-ID: <d1c3259e-d29f-4d7d-8a5b-dabd469a7c7c@linux.intel.com> (raw)
In-Reply-To: <d01c8939-0555-4810-8995-849d33a00085@linux.intel.com>
Applied to drm-misc-next
On 10/1/2025 9:50 AM, Karol Wachowski wrote:
> Reviewed-by: Karol Wachowski <karol.wachowski@linux.intel.com>
>
> On 9/25/2025 4:51 PM, Maciej Falkowski wrote:
>> From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
>>
>> Don't add BO to the vdev->bo_list in ivpu_gem_create_object().
>> When failure happens inside drm_gem_shmem_create(), the BO is not
>> fully created and ivpu_gem_bo_free() callback will not be called
>> causing a deleted BO to be left on the list.
>>
>> Fixes: 8d88e4cdce4f ("accel/ivpu: Use GEM shmem helper for all buffers")
>> Signed-off-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
>> Signed-off-by: Maciej Falkowski <maciej.falkowski@linux.intel.com>
>> ---
>> drivers/accel/ivpu/ivpu_gem.c | 22 ++++++++++++++++------
>> 1 file changed, 16 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/accel/ivpu/ivpu_gem.c b/drivers/accel/ivpu/ivpu_gem.c
>> index 0cb48aff396c..38ecf933d144 100644
>> --- a/drivers/accel/ivpu/ivpu_gem.c
>> +++ b/drivers/accel/ivpu/ivpu_gem.c
>> @@ -194,7 +194,6 @@ void ivpu_bo_unbind_all_bos_from_context(struct ivpu_device *vdev, struct ivpu_m
>>
>> struct drm_gem_object *ivpu_gem_create_object(struct drm_device *dev, size_t size)
>> {
>> - struct ivpu_device *vdev = to_ivpu_device(dev);
>> struct ivpu_bo *bo;
>>
>> if (size == 0 || !PAGE_ALIGNED(size))
>> @@ -209,20 +208,17 @@ struct drm_gem_object *ivpu_gem_create_object(struct drm_device *dev, size_t siz
>>
>> INIT_LIST_HEAD(&bo->bo_list_node);
>>
>> - mutex_lock(&vdev->bo_list_lock);
>> - list_add_tail(&bo->bo_list_node, &vdev->bo_list);
>> - mutex_unlock(&vdev->bo_list_lock);
>> -
>> - ivpu_dbg(vdev, BO, " alloc: bo %8p size %9zu\n", bo, size);
>> return &bo->base.base;
>> }
>>
>> struct drm_gem_object *ivpu_gem_prime_import(struct drm_device *dev,
>> struct dma_buf *dma_buf)
>> {
>> + struct ivpu_device *vdev = to_ivpu_device(dev);
>> struct device *attach_dev = dev->dev;
>> struct dma_buf_attachment *attach;
>> struct drm_gem_object *obj;
>> + struct ivpu_bo *bo;
>> int ret;
>>
>> attach = dma_buf_attach(dma_buf, attach_dev);
>> @@ -240,6 +236,14 @@ struct drm_gem_object *ivpu_gem_prime_import(struct drm_device *dev,
>> obj->import_attach = attach;
>> obj->resv = dma_buf->resv;
>>
>> + bo = to_ivpu_bo(obj);
>> +
>> + mutex_lock(&vdev->bo_list_lock);
>> + list_add_tail(&bo->bo_list_node, &vdev->bo_list);
>> + mutex_unlock(&vdev->bo_list_lock);
>> +
>> + ivpu_dbg(vdev, BO, "import: bo %8p size %9zu\n", bo, ivpu_bo_size(bo));
>> +
>> return obj;
>>
>> fail_detach:
>> @@ -270,6 +274,12 @@ static struct ivpu_bo *ivpu_bo_alloc(struct ivpu_device *vdev, u64 size, u32 fla
>> bo->base.map_wc = flags & DRM_IVPU_BO_WC;
>> bo->flags = flags;
>>
>> + mutex_lock(&vdev->bo_list_lock);
>> + list_add_tail(&bo->bo_list_node, &vdev->bo_list);
>> + mutex_unlock(&vdev->bo_list_lock);
>> +
>> + ivpu_dbg(vdev, BO, " alloc: bo %8p size %9llu\n", bo, size);
>> +
>> return bo;
>> }
>>
prev parent reply other threads:[~2025-10-01 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 14:51 [PATCH] accel/ivpu: Fix page fault in ivpu_bo_unbind_all_bos_from_context() Maciej Falkowski
2025-10-01 7:50 ` Karol Wachowski
2025-10-01 8:03 ` Karol Wachowski [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=d1c3259e-d29f-4d7d-8a5b-dabd469a7c7c@linux.intel.com \
--to=karol.wachowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=lizhi.hou@amd.com \
--cc=maciej.falkowski@linux.intel.com \
--cc=oded.gabbay@gmail.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