From: Stefano Garzarella <[email protected]> Date: Wed, 26 Feb 2020 11:58:18 +0100
> Some transports (hyperv, virtio) acquire the sock lock during the > .release() callback. > > In the vsock_stream_connect() we call vsock_assign_transport(); if > the socket was previously assigned to another transport, the > vsk->transport->release() is called, but the sock lock is already > held in the vsock_stream_connect(), causing a deadlock reported by > syzbot: ... > To avoid this issue, this patch remove the lock acquiring in the > .release() callback of hyperv and virtio transports, and it holds > the lock when we call vsk->transport->release() in the vsock core. > > Reported-by: [email protected] > Fixes: 408624af4c89 ("vsock: use local transport when it is loaded") > Signed-off-by: Stefano Garzarella <[email protected]> Applied, thank you. _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
