Ondřej Surý 94afea9325 Don't use stack allocated buffer for uv_write() ...

On FreeBSD, the stack is destroyed more aggressively than on Linux and
that revealed a bug where we were allocating the 16-bit len for the
TCPDNS message on the stack and the buffer got garbled before the
uv_write() sendback was executed.  Now, the len is part of the uvreq, so
we can safely pass it to the uv_write() as the req gets destroyed after
the sendcb is executed.

2020-12-03 08:58:16 +01:00

..

netmgr-int.h

Don't use stack allocated buffer for uv_write()

2020-12-03 08:58:16 +01:00

netmgr.c

Make netmgr initialize and cleanup Winsock itself

2020-12-02 22:36:23 +01:00

tcp.c

Fix the data race in accessing the isc_nm_t timers

2020-12-02 10:14:31 +01:00

tcpdns.c

Don't use stack allocated buffer for uv_write()

2020-12-03 08:58:16 +01:00

tls.c

Fix the data race in accessing the isc_nm_t timers

2020-12-02 10:14:31 +01:00

tlsdns.c

Fix the data race in accessing the isc_nm_t timers

2020-12-02 10:14:31 +01:00

udp.c

Avoid netievent allocations when the callbacks can be called directly

2020-12-02 09:45:05 +01:00

uv-compat.c

Refactor netmgr and add more unit tests

2020-12-01 16:47:07 +01:00

uv-compat.h

Refactor netmgr and add more unit tests

2020-12-01 16:47:07 +01:00

uverr2result.c

Refactor netmgr and add more unit tests

2020-12-01 16:47:07 +01:00