Re: [PATCH] module: debugging check for runaway kthreads

2012-03-01 Thread Rusty Russell
On Wed, 29 Feb 2012 19:21:13 +0400, Dmitry Antipov 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 followin

Re: [RFC PATCH] module: debugging check for runaway kthreads

2012-02-29 Thread Andrew Morton
On Tue, 28 Feb 2012 13:04:23 +0400 Dmitry Antipov 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

[PATCH] module: debugging check for runaway kthreads

2012-02-29 Thread Dmitry Antipov
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 cat

Re: [RFC PATCH] module: debugging check for runaway kthreads

2012-02-29 Thread Dmitry Antipov
On 02/29/2012 12:43 AM, Andrew Morton wrote: Please make the stub function a proper C function, not a macro. It provides type checking, can prevent compile warnings and is generally easier on the eyes. OK I think this should be under the kernel hacking menu, dependent on CONFIG_DEBUG_KERNEL

[RFC PATCH] module: debugging check for runaway kthreads

2012-02-28 Thread Dmitry Antipov
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 cat

[PATCH] module: debugging check for runaway kthreads

2012-02-02 Thread Dmitry Antipov
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. See http://marc.info/?l=linux-kernel&m=132811276131767&w=2 to check why it migh