CHROMIUM: virtio/wl: Fix a missing mutex unlock in error path
The mutex is going to be freed, so it does not lead to a deadlock, but
it can confuse lock debugging tools.
BUG=none
TEST=compile (the error does not normally happen)
Reported-by: Dmitry Torokhov <dtor@chromium.org>
Change-Id: I8ea3905ed78f559a038868d4230612b9d0496dd0
Signed-off-by: Tomasz Figa <tfiga@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1159921
Reviewed-by: Zach Reizner <zachr@chromium.org>
diff --git a/drivers/virtio/virtio_wl.c b/drivers/virtio/virtio_wl.c
index 553b81d..61fee3a 100644
--- a/drivers/virtio/virtio_wl.c
+++ b/drivers/virtio/virtio_wl.c
@@ -955,7 +955,7 @@
ret = idr_alloc(&vi->vfds, vfd, 1, VIRTWL_MAX_ALLOC, GFP_KERNEL);
mutex_unlock(&vi->vfds_lock);
if (ret <= 0)
- goto free_vfd;
+ goto remove_vfd;
vfd->id = ret;
ret = 0;
@@ -1023,10 +1023,14 @@
return vfd;
remove_vfd:
- /* unlock the vfd to avoid deadlock when unlinking it */
+ /*
+ * unlock the vfd to avoid deadlock when unlinking it
+ * or freeing a held lock
+ */
mutex_unlock(&vfd->lock);
- virtwl_vfd_lock_unlink(vfd);
-free_vfd:
+ /* this is safe since the id cannot change after the vfd is created */
+ if (vfd->id)
+ virtwl_vfd_lock_unlink(vfd);
virtwl_vfd_free(vfd);
free_ctrl_new:
kfree(ctrl_new);
