Bug: deadlock from msyslog

Hal Murray hmurray at megapathdsl.net
Wed Jan 20 10:31:29 UTC 2016

A while (months) ago, we had troubles with msyslog scrambling output when 
called from the DNS thread and the main thread at the same time.  That was 
fixed by adding a lock.

That will deadlock if a signal handler calls msyslog when the signal goes off 
in the middle of a msyslog call.

I poked around a bit.  There are a few signal handlers that call msyslog.  I 
think they can be deferred.  It's probably worthwhile to study all the signal 
usage and make some notes.

The only timing critical signal handler that I know about would be the one 
grabbing the time of received packets.  That code doesn't get enabled by our 
current build system.  NTP Classic uses it on NetBSD.

These are my opinions.  I hate spam.

More information about the devel mailing list