Strange behaviour from kernel thread

Hi all,

i am working on a project with kernel threads. And I get this strange behaviour.

At first, i create the thread directly after the kernel module is loaded. This work perfectly as i create and ends the thread.

But then if i try to create the kernel threads later after the module is loaded, for example by writing the proc file system of the kernel module, the thread later can not be ended by sending signal (with kill_proc() function) as i unload the module.

The thread somehow doesn't receive the signal if i create them from write proc file system (echo "command > /proc/mymodule). But in the first case, i i create them directly as the kernel module loaded, it does receive the signal.

any hints about this problem?

thanks,

Futzed-up the thread-ID somehow?

Originally Posted by sundialsvcs Futzed-up the thread-ID somehow?

How could it be possible? or maybe if i create the threads in write proc file system, the parrent process is not my kernel module? is it possible?

thanks for the hints,