Mark Andrews 363b40b1da 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-19 11:28:10 +01:00
..
bind9	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
dns	Don't use reference counting in isc_timer unit	2023-01-19 11:28:10 +01:00
irs	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
isc	Unlink the timer event before trying to purge it	2023-01-19 11:28:10 +01:00
isccc	Update sources to Clang 15 formatting	2022-11-29 10:30:34 +01:00
isccfg	deprecate dscp configuration	2023-01-10 11:16:18 -08:00
ns	Check for NULL before dereferencing qctx->rpz_st	2023-01-09 13:57:44 +01:00
win32/bindevt	Update the copyright information in all files in the repository	2022-01-11 12:22:09 +01:00
.gitignore
Kyuafile	Update the copyright information in all files in the repository	2022-01-11 12:22:09 +01:00
Makefile.in	Update the copyright information in all files in the repository	2022-01-11 12:22:09 +01:00