diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2016-06-23 16:28:58 +0100 |
|---|---|---|
| committer | Alistair Strachan <astrachan@google.com> | 2019-01-15 17:08:34 -0800 |
| commit | a598d93c2a3ab180d9a52ad15fcf023a1ee897d8 (patch) | |
| tree | c5beac3a22a04fb1aebf176fbe1ec89d67a12df3 /build.config.cuttlefish.aarch64 | |
| parent | 0f0ec3accb21ac2f7e510c44326294bd4164fc19 (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 'build.config.cuttlefish.aarch64')
0 files changed, 0 insertions, 0 deletions