habanalabs: fix vma fields assignments order in hl_hw_block_mmap()

In hl_hw_block_mmap(), the vma's 'vm_private_data' and 'vm_ops' fields
are assigned before filling the content of the private data.
In between there is a call to the ASIC hw_block_mmap() function, and if
it fails, the vma close function will be called with a bad private data
value.
Fix the order of assignments to avoid this issue.

In hl_hw_block_mmap() the vma's 'vm_private_data and vm_ops are assigned
before setting the

Signed-off-by: Tomer Tayar <ttayar@habana.ai>
Reviewed-by: Oded Gabbay <ogabbay@kernel.org>
Signed-off-by: Oded Gabbay <ogabbay@kernel.org>

diff --git a/drivers/misc/habanalabs/common/memory.c b/drivers/misc/habanalabs/common/memory.c
index 0698c3c..a027fa8 100644 (file)
--- a/drivers/misc/habanalabs/common/memory.c
+++ b/drivers/misc/habanalabs/common/memory.c
@@ -1492,23 +1492,22 @@ int hl_hw_block_mmap(struct hl_fpriv *hpriv, struct vm_area_struct *vma)
        if (!lnode)
                return -ENOMEM;
 
-       vma->vm_ops = &hw_block_vm_ops;
-       vma->vm_private_data = lnode;
-
-       hl_ctx_get(ctx);
-
        rc = hdev->asic_funcs->hw_block_mmap(hdev, vma, block_id, block_size);
        if (rc) {
-               hl_ctx_put(ctx);
                kfree(lnode);
                return rc;
        }
 
+       hl_ctx_get(ctx);
+
        lnode->ctx = ctx;
        lnode->vaddr = vma->vm_start;
        lnode->size = block_size;
        lnode->id = block_id;
 
+       vma->vm_private_data = lnode;
+       vma->vm_ops = &hw_block_vm_ops;
+
        mutex_lock(&ctx->hw_block_list_lock);
        list_add_tail(&lnode->node, &ctx->hw_block_mem_list);
        mutex_unlock(&ctx->hw_block_list_lock);