On Fri, Jun 05, 2015 at 05:00:59PM +0200, Petr Mladek wrote: > Kthreads are implemented as an infinite loop. They include check points > for termination, freezer, parking, and even signal handling. > > We need to touch all kthreads every time we want to add or > modify the behavior of such checkpoints. It is not easy because > there are several hundreds of kthreads and each of them is > implemented in a slightly different way. > > This anarchy brings potentially broken or non-standard behavior. > For example, few kthreads already handle signals a strange way. > > > This patchset is a _proof-of-concept_ how to improve the situation.
Maybe it might be a better idea to audit the existing callers of signals for kthreads and first check if we can get rid of them. Then as a second step if any are left convert them to signalfd-style operation where signals aren't checked synchronously but as something the threads can consume on a as needed basis. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
