Mark Andrews 80a052aaf6 Unlink the timer event before trying to purge it ... as far as I can determine the order of operations is not important. *** CID 351372: Concurrent data access violations (ATOMICITY) /lib/isc/timer.c: 227 in timer_purge() 221 LOCK(&timer->lock); 222 if (!purged) { 223 /* 224 * The event has already been executed, but not 225 * yet destroyed. 226 */ >>> CID 351372: Concurrent data access violations (ATOMICITY) >>> Using an unreliable value of "event" inside the second locked section. If the data that "event" depends on was changed by another thread, this use might be incorrect. 227 timerevent_unlink(timer, event); 228 } 229 } 230 } 231 232 void (cherry picked from commit 98718b3b4b)		2023-01-18 22:39:26 +01:00
..
bind9	remove nonfunctional DSCP implementation	2023-01-09 14:23:26 -08:00
dns	Don't use reference counting in isc_timer unit	2023-01-18 22:39:26 +01:00
irs	Move all the unit tests to /tests/<libname>/	2022-05-31 12:06:00 +02:00
isc	Unlink the timer event before trying to purge it	2023-01-18 22:39:26 +01:00
isccc	Update sources to Clang 15 formatting	2022-11-29 09:14:07 +01:00
isccfg	remove nonfunctional DSCP implementation	2023-01-09 14:23:26 -08:00
ns	Don't set EDE in ns_client_aclchecksilent	2023-01-10 10:02:14 +00: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