vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()
commitbd3ccdc6f922c6b7db4b7075d1b6596ddb986a98
authorJason Wang <jasowang@redhat.com>
Tue, 23 Jan 2018 09:27:25 +0000 (23 17:27 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 25 Feb 2018 10:05:39 +0000 (25 11:05 +0100)
tree9a4234c9f218b9ab2caa0c3cc5a1f555d7e9ea86
parent80c1c8322c331586a86e58d3f95026a1265ab396
vhost: use mutex_lock_nested() in vhost_dev_lock_vqs()

commit e9cb4239134c860e5f92c75bf5321bd377bb505b upstream.

We used to call mutex_lock() in vhost_dev_lock_vqs() which tries to
hold mutexes of all virtqueues. This may confuse lockdep to report a
possible deadlock because of trying to hold locks belong to same
class. Switch to use mutex_lock_nested() to avoid false positive.

Fixes: 6b1e6cc7855b0 ("vhost: new device IOTLB API")
Reported-by: syzbot+dbb7c1161485e61b0241@syzkaller.appspotmail.com
Signed-off-by: Jason Wang <jasowang@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/vhost/vhost.c