Stefan Hajnoczi 4192f672fa vsock: make listener child lock ordering explicit ... There are several places where the listener and pending or accept queue child sockets are accessed at the same time. Lockdep is unhappy that two locks from the same class are held. Tell lockdep that it is safe and document the lock ordering. Originally Claudio Imbrenda <imbrenda@linux.vnet.ibm.com> sent a similar patch asking whether this is safe. I have audited the code and also covered the vsock_pending_work() function. Suggested-by: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2016-06-27 10:44:46 -04:00
..
af_vsock.c	vsock: make listener child lock ordering explicit	2016-06-27 10:44:46 -04:00
Kconfig	Revert "Merge branch 'vsock-virtio'"	2015-12-08 21:55:49 -05:00
Makefile	Revert "Merge branch 'vsock-virtio'"	2015-12-08 21:55:49 -05:00
vmci_transport_notify_qstate.c	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vmci_transport_notify.c	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vmci_transport_notify.h	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vmci_transport.c	VSOCK: constify vsock_transport structure	2016-05-03 13:03:05 -04:00
vmci_transport.h	VSOCK: constify vmci_transport_notify_ops structures	2015-11-23 15:49:29 -05:00
vsock_addr.c