From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH] drm/xe: Fix vm refcount races
Date: Thu, 25 May 2023 09:41:44 +0200 [thread overview]
Message-ID: <20230525074144.178961-1-thomas.hellstrom@linux.intel.com> (raw)
Fix a race in xe_vm_lookup() where the vm could disappear after
the lookup mutex unlock but before the get. The xe_vm_get() call
must be inside the lookup mutex.
Also fix a vm close race where multiple callers could potentially
succeed in calling xe_vm_close_and_put().
Reported-by: Oded Gabbay <ogabbay@kernel.org>
Link: https://lists.freedesktop.org/archives/intel-xe/2023-May/004704.html
Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
drivers/gpu/drm/xe/xe_vm.c | 26 ++++++++++++--------------
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
index a0306526b269..ac25afac89fd 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -1463,10 +1463,9 @@ struct xe_vm *xe_vm_lookup(struct xe_file *xef, u32 id)
mutex_lock(&xef->vm.lock);
vm = xa_load(&xef->vm.xa, id);
- mutex_unlock(&xef->vm.lock);
-
if (vm)
xe_vm_get(vm);
+ mutex_unlock(&xef->vm.lock);
return vm;
}
@@ -1940,26 +1939,25 @@ int xe_vm_destroy_ioctl(struct drm_device *dev, void *data,
struct xe_file *xef = to_xe_file(file);
struct drm_xe_vm_destroy *args = data;
struct xe_vm *vm;
+ int err = 0;
if (XE_IOCTL_ERR(xe, args->pad))
return -EINVAL;
- vm = xe_vm_lookup(xef, args->vm_id);
- if (XE_IOCTL_ERR(xe, !vm))
- return -ENOENT;
- xe_vm_put(vm);
-
- /* FIXME: Extend this check to non-compute mode VMs */
- if (XE_IOCTL_ERR(xe, vm->preempt.num_engines))
- return -EBUSY;
-
mutex_lock(&xef->vm.lock);
- xa_erase(&xef->vm.xa, args->vm_id);
+ vm = xa_load(&xef->vm.xa, args->vm_id);
+ if (XE_IOCTL_ERR(xe, !vm))
+ err = -ENOENT;
+ else if (XE_IOCTL_ERR(xe, vm->preempt.num_engines))
+ err = -EBUSY;
+ else
+ xa_erase(&xef->vm.xa, args->vm_id);
mutex_unlock(&xef->vm.lock);
- xe_vm_close_and_put(vm);
+ if (!err)
+ xe_vm_close_and_put(vm);
- return 0;
+ return err;
}
static const u32 region_to_mem_type[] = {
--
2.39.2
next reply other threads:[~2023-05-25 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 7:41 Thomas Hellström [this message]
2023-05-25 7:43 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Fix vm refcount races Patchwork
2023-05-25 7:45 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-25 7:49 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-25 8:18 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-05-25 21:35 ` [Intel-xe] [PATCH] " Matthew Brost
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=20230525074144.178961-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.