https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200493
--- Comment #8 from Konstantin Belousov <k...@freebsd.org> --- (In reply to Konstantin Belousov from comment #7) And to express my opinion on the whole stuff. The signal delivery to the kernel threads must be opt-in feature. Kernel thread should explicitely declare the ability to handle signals directed to it. E.g., nfsd threads check for signal as an indication of exit request. Most threads do not handle signals at all, and queuing the signal to them causes odd side-effects. Most innocent consequence is the memory leak due to queued ksiginfo, which is never deleted from the sigqueue. Or, the priority bump for the idle thread, as you discovered. Code to prevent even queuing signals to the kernel threads is trivial, but it requires careful examination of each call to kproc/kthread creation to decide should the signalling be allowed. The patch I provided IMO is good stop-gap measure which fixes the immediate ugly case. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
