Closed aler9 closed 11 months ago
Thanks for pointing this out. All the writes to the statistics must be protected because of the conn.Stats()
function which is reading the statistics. In datarhei/gosrt@da138d1 I introduced a dedicated lock for the statistics. Using the c.cryptoLock
is confusing.
A dedicated lock is the best option, i didn't do it because i did not want to add additional resources without a good reason.
Hello,
sendNACK()
is called by bothrecv.Tick()
andrecv.Push()
in two separate routines, the operationpktSentNAK++
is not atomic (it gets compiled into a read command followed by a write command) and must be protected.