diff options
| author | Bhasker Hariharan <bhaskerh@google.com> | 2020-01-15 13:20:14 -0800 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2020-01-15 13:21:50 -0800 |
| commit | 275ac8ce1debf89a22eb1150df3bf9ba7a0bc9ba (patch) | |
| tree | 3f96c3a08e2cc4fb100d70e4c5f56251508f55d4 /test/syscalls/linux/fadvise64.cc | |
| parent | f874723e64bd8a2e747bb336e0b6b8f0da1f044a (diff) | |
Bugfix to terminate the protocol loop on StateError.
The change to introduce worker goroutines can cause the endpoint
to transition to StateError and we should terminate the loop rather
than let the endpoint transition to a CLOSED state as we do
in case the endpoint enters TIME-WAIT/CLOSED. Moving to a closed
state would cause the actual error to not be propagated to
any read() calls etc.
PiperOrigin-RevId: 289923568
Diffstat (limited to 'test/syscalls/linux/fadvise64.cc')
0 files changed, 0 insertions, 0 deletions