diff options
| author |   Jason A. Donenfeld <Jason@zx2c4.com> | 2021-01-07 15:56:52 +0100 |
|---|---|---|
| committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2021-01-07 17:08:41 +0100 |
| commit | 29b04775856b62213d7bc01937641e2db081d707 (patch) | |
| tree | 6044865a29772209154acd59ba7f66274a623403 /conn | |
| parent | device: add latency and throughput benchmarks (diff) | |
| download | wireguard-go-29b04775856b62213d7bc01937641e2db081d707.tar.xz wireguard-go-29b04775856b62213d7bc01937641e2db081d707.zip | |
device: receive: drain decryption queue before exiting RoutineDecryption
It's possible for RoutineSequentialReceiver to try to lock an elem after
RoutineDecryption has exited. Before this meant we didn't then unlock
the elem, so the whole program deadlocked.
As well, it looks like the flush code (which is now potentially
unnecessary?) wasn't properly dropping the buffers for the
not-already-dropped case.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'conn')
0 files changed, 0 insertions, 0 deletions