wireguard-go/device/send.go, branch js/sample-api

device: add missing colon to error line

2020-12-18T19:18:47Z

People are actually hitting this condition, so make it uniform. Also, change a printf into a println, to match the other conventions. Signed-off-by: Jason A. Donenfeld

device: fix races from changing private_key

2020-12-17T00:16:26Z

Access keypair.sendNonce atomically. Eliminate one unnecessary initialization to zero. Mutate handshake.lastSentHandshake with the mutex held. Co-authored-by: David Anderson Signed-off-by: Josh Bleecher Snyder

device: always name QueueElement variables elem

2020-12-17T00:16:26Z

They're called elem in most places. Rename a few local variables to make it consistent. This makes it easier to grep the code for things like elem.Drop. Signed-off-by: Josh Bleecher Snyder

device: use channel close to shut down and drain outbound channel

2020-12-17T00:16:26Z

This is a similar treatment to the handling of the encryption channel found a few commits ago: Use the closing of the channel to manage goroutine lifetime and shutdown. It is considerably simpler because there is only a single writer. Signed-off-by: Josh Bleecher Snyder

device: use channel close to shut down and drain encryption channel

2020-12-16T00:57:09Z

The new test introduced in this commit used to deadlock about 1% of the time. I believe that the deadlock occurs as follows: * The test completes, calling device.Close. * device.Close closes device.signals.stop. * RoutineEncryption stops. * The deferred function in RoutineEncryption drains device.queue.encryption. * RoutineEncryption exits. * A peer's RoutineNonce processes an element queued in peer.queue.nonce. * RoutineNonce puts that element into the outbound and encryption queues. * RoutineSequentialSender reads that elements from the outbound queue. * It waits for that element to get Unlocked by RoutineEncryption. * RoutineEncryption has already exited, so RoutineSequentialSender blocks forever. * device.RemoveAllPeers calls peer.Stop on all peers. * peer.Stop waits for peer.routines.stopping, which blocks forever. Rather than attempt to add even more ordering to the already complex centralized shutdown orchestration, this commit moves towards a data-flow-oriented shutdown. The device.queue.encryption gets closed when there will be no more writes to it. All device.queue.encryption readers always read until the channel is closed and then exit. We thus guarantee that any element that enters the encryption queue also exits it. This removes the need for central control of the lifetime of RoutineEncryption, removes the need to drain the encryption queue on shutdown, and simplifies RoutineEncryption. This commit also fixes a data race. When RoutineSequentialSender drains its queue on shutdown, it needs to lock the elem before operating on it, just as the main body does. The new test in this commit passed 50k iterations with the race detector enabled and 150k iterations with the race detector disabled, with no failures. Signed-off-by: Josh Bleecher Snyder

device: remove starting waitgroups

2020-12-10T21:37:10Z

In each case, the starting waitgroup did nothing but ensure that the goroutine has launched. Nothing downstream depends on the order in which goroutines launch, and if the Go runtime scheduler is so broken that goroutines don't get launched reasonably promptly, we have much deeper problems. Given all that, simplify the code. Passed a race-enabled stress test 25,000 times without failure. Signed-off-by: Josh Bleecher Snyder

device: clear pointers when returning elems to pools

2020-12-08T22:25:02Z

Signed-off-by: Josh Bleecher Snyder

device: use labeled for loop instead of goto

2020-12-08T22:24:20Z

Minor code cleanup; no functional changes. Signed-off-by: Josh Bleecher Snyder

device: add write queue mutex for peer

2020-11-18T13:22:15Z

fix panic: send on closed channel when remove peer Signed-off-by: Haichao Liu Signed-off-by: Jason A. Donenfeld

device: rework padding calculation and don't shadow paddedSize

2020-05-18T21:43:22Z

Reported-by: Jayakumar S Signed-off-by: Jason A. Donenfeld

wireguard-go/device/send.go, branch js/sample-api

device: add missing colon to error line

device: fix races from changing private_key

device: always name *Queue*Element variables elem

device: use channel close to shut down and drain outbound channel

device: use channel close to shut down and drain encryption channel

device: remove starting waitgroups

device: clear pointers when returning elems to pools

device: use labeled for loop instead of goto

device: add write queue mutex for peer

device: rework padding calculation and don't shadow paddedSize

device: always name QueueElement variables elem