diff options
author | Stefan Hajnoczi <stefanha@redhat.com> | 2016-06-23 16:28:58 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-06-27 10:44:46 -0400 |
commit | 4192f672fae559f32d82de72a677701853cc98a7 (patch) | |
tree | 40510d67dd103d5a44cf345706ed92d6407da300 /crypto/jitterentropy-kcapi.c | |
parent | 48f1dcb55a7d29aeb8965c567660c14d0dfd1a42 (diff) | |
download | linux-stable-4192f672fae559f32d82de72a677701853cc98a7.tar.gz linux-stable-4192f672fae559f32d82de72a677701853cc98a7.tar.bz2 linux-stable-4192f672fae559f32d82de72a677701853cc98a7.zip |
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>
Diffstat (limited to 'crypto/jitterentropy-kcapi.c')
0 files changed, 0 insertions, 0 deletions