Closed InterLinked1 closed 1 year ago
May or may not be related, but logging can also get stuck here due to write
blocking forever:
RWLIST_RDLOCK(&remote_log_fds);
RWLIST_TRAVERSE(&remote_log_fds, rfd, entry) {
if (fd_logging[rfd->fd]) {
write(rfd->fd, fullbuf, (size_t) bytes);
}
}
RWLIST_UNLOCK(&remote_log_fds);
If any remote consoles are active at shutdown, any attempts to shutdown or restart (whether from the foreground or a remote console) will cause a segfault during module unload. No segfault when replicated with valgrind.
This is likely more serious memory corruption since there appears to be stack corruption in the backtrace, no further details are available:
Other threads appear to be all right, which is a strong hint this is corruption caused when trying to unload
mod_sysop
. Possibly related to recent changes to try to move away frompthread_cancel
in that module and some others?