[PATCH] module: debugging check for runaway kthreads

Rusty Russell rusty at ozlabs.org
Thu Mar 1 01:36:54 UTC 2012

On Wed, 29 Feb 2012 19:21:13 +0400, Dmitry Antipov <dmitry.antipov at linaro.org> wrote:
> Debugging option CONFIG_MODULE_KTHREAD_CHECK provides a way to check
> whether all kernel threads created by the module and have used module
> code as a thread worker function are really exited when the module is
> unloaded. The following pseudo-code contains example of an error which
> is likely to be catched with this debugging check:

Nice idea, but that's 101 lines of code, for very little gain.

How about a debug option which unmaps all module pages on removal,
and ensures they don't get reused?  That might catch a multitude of
problems.  And yes, I realize it might be a bigger patch...


More information about the linaro-dev mailing list