Evan Hunt 9c577e10c3 use separate barriers for "stop" and "listen" operations ... On some platforms, when a synchronizing barrier is cleared, one thread can progress while other threads are still in the process of releasing the barrier. If a barrier is reused by the progressing thread during this window, it can cause a deadlock. This can occur if, for example, we stop listening immediately after we start, because the stop and listen functions both use socket->barrier. This has been addressed by using separate barrier objects for stop and listen.		2023-01-07 16:30:21 -08:00
..
bind9	Update sources to Clang 15 formatting	2022-11-29 08:54:34 +01:00
dns	Deduplicate DNS_RBTDB_STRONG_RWLOCK_CHECK macros	2023-01-06 08:56:31 +01:00
irs	Move all the unit tests to /tests/<libname>/	2022-05-28 14:53:02 -07:00
isc	use separate barriers for "stop" and "listen" operations	2023-01-07 16:30:21 -08:00
isccc	Change the isc_buffer_reserve() to take just buffer pointer	2022-12-20 19:13:48 +01:00
isccfg	Remove setting alternate transfer source	2022-12-23 14:39:59 +01:00
ns	BIND: use Stream DNS for DNS over TCP connections	2022-12-20 22:13:53 +02:00
.gitignore	The isc/platform.h header has been completely removed	2021-07-06 05:33:48 +00:00
Makefile.am	move samples/resolve.c to bin/tests/system	2021-04-16 14:29:43 +02:00