VSOCK: Fix lockdep issue.
The recent fix for the vsock sock_put issue used the wrong initializer for the transport spin_lock causing an issue when running with lockdep checking. Testing: Verified fix on kernel with lockdep enabled. Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com> Signed-off-by: Jorgen Hansen <jhansen@vmware.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
0db65fcfcd
commit
8566b86ab9
|
@ -1570,7 +1570,7 @@ static int vmci_transport_socket_init(struct vsock_sock *vsk,
|
||||||
vmci_trans(vsk)->notify_ops = NULL;
|
vmci_trans(vsk)->notify_ops = NULL;
|
||||||
INIT_LIST_HEAD(&vmci_trans(vsk)->elem);
|
INIT_LIST_HEAD(&vmci_trans(vsk)->elem);
|
||||||
vmci_trans(vsk)->sk = &vsk->sk;
|
vmci_trans(vsk)->sk = &vsk->sk;
|
||||||
vmci_trans(vsk)->lock = __SPIN_LOCK_UNLOCKED(vmci_trans(vsk)->lock);
|
spin_lock_init(&vmci_trans(vsk)->lock);
|
||||||
if (psk) {
|
if (psk) {
|
||||||
vmci_trans(vsk)->queue_pair_size =
|
vmci_trans(vsk)->queue_pair_size =
|
||||||
vmci_trans(psk)->queue_pair_size;
|
vmci_trans(psk)->queue_pair_size;
|
||||||
|
|
Loading…
Reference in New Issue