mirror of
https://github.com/zrepl/zrepl.git
synced 2025-01-08 23:39:04 +01:00
d118bcc717
- `timeoutconn` handles state, yet calls to Read/Write make a copy of
that state (non-pointer receiver) so any outbound calls will not have
the state updated
- Even without the copy issue, the renew methods can in edge cases set a
new deadline _after_ DisableTimeouts have been called, consider the
following racy behavior:
1. `renewReadDeadline` is called, checks `renewDeadlinesDisabled`
(not disabled)
2. `DisableTimeouts` is called, sets `renewDeadlinesDisabled`
3. `DisableTimeouts` invokes `c.SetDeadline`
4. `renewReadDeadline` invokes `c.SetReadDeadline`
To fix the above, the `Conn` receiver was made to be a pointer
everywhere and access to renewDeadlinesDisabled is now guarded
by an RWMutex instead of using atomics.
closes #415
|
||
|---|---|---|
| .. | ||
| base2bufpool | ||
| frameconn | ||
| heartbeatconn | ||
| microbenchmark | ||
| stream | ||
| timeoutconn | ||
| dataconn_client.go | ||
| dataconn_debug.go | ||
| dataconn_server.go | ||
| dataconn_shared.go | ||
| dataconn_test.go | ||