a515fc517b
Running corp/ipn#TestNetworkLockE2E has a 1/300 chance of failing, and deskchecking suggests thats whats happening are two netmaps are racing each other to be processed through tkaSyncIfNeededLocked. This happens in the first place because we release b.mu during network RPCs. To fix this, we make the tka sync logic an exclusive section, so two netmaps will need to wait for tka sync to complete serially (which is what we would want anyway, as the second run through probably wont need to sync). Signed-off-by: Tom DNetto <tom@tailscale.com> |
||
|---|---|---|
| .. | ||
| c2n.go | ||
| dnsconfig_test.go | ||
| local.go | ||
| local_test.go | ||
| loglines_test.go | ||
| network-lock.go | ||
| network-lock_test.go | ||
| peerapi.go | ||
| peerapi_h2c.go | ||
| peerapi_macios_ext.go | ||
| peerapi_test.go | ||
| ssh.go | ||
| ssh_stub.go | ||
| ssh_test.go | ||
| state_test.go | ||