![]() | |||||||||||||
Messages in this thread |
Once upon a time, kernel threads could make use of signals for receiving control from userspace. Now, the NPTL code looks at the recipient thread's userspace handlers for signals, even in the case of a kernel thread, and if there's not a handler installed will either discard the signal or convert it to SIGKILL. Could we disable this behaviour in the case where the recipient is a kernel thread please? Or at least make allow_signal() set sa_handler to some non-zero dummy value so that the signal is delivered as intended. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:49 [from the cache] ©2003-2008 | |||||||||||||