summaryrefslogtreecommitdiff
path: root/lib/clz_tab.c
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@redhat.com>2016-06-23 16:28:58 +0100
committerAlistair Strachan <astrachan@google.com>2019-05-14 17:56:56 -0700
commitd279af442001d03b41af233e97549f4b23d403a0 (patch)
tree54bb025f81a01ec093a5278fcd6bd9acf34c65a6 /lib/clz_tab.c
parentef6c5bb7eb80e44863fd54f97a77ed7e21b57dc8 (diff)
UPSTREAM: 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> (cherry picked from commit 4192f672fae559f32d82de72a677701853cc98a7) Bug: 121166534 Test: Ran cuttlefish with android-4.4 + VSOCKETS, VMWARE_VMCI_VSOCKETS Signed-off-by: Cody Schuffelen <schuffelen@google.com> Change-Id: I0cb7ee964057e9338971e1a2043ae17557feaec7
Diffstat (limited to 'lib/clz_tab.c')
0 files changed, 0 insertions, 0 deletions