Re: Stopping Kernel Threads at module unload time

Hello,

> This is how the kernel thread is stopped.
>
>      if(info->pid)
>      {
>          (void)kill_proc(info->pid, SIGTERM, 1);
>          wait_for_completion(&info->quit);
>      }
>

I actually would prefer to do it with the new kernel thread API.
So, to create the thread:   kthread_create
bind it to a cpu:                  kthread_bind
stop it:                                kthread_stop

Now, if I call kthread_stop() in module unload time, does that code
run in user process context just like system calls do? That is
important, because if it cannot sleep, it would deadlock.
-
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/

---

• Follow-Ups:
  • Re: Stopping Kernel Threads at module unload time
    • From: Arnd Bergmann <[email protected]>
  • Re: Stopping Kernel Threads at module unload time
    • From: "linux-os \(Dick Johnson\)" <[email protected]>

• References:
  • Stopping Kernel Threads at module unload time
    • From: Aritz Bastida <[email protected]>
  • Re: Stopping Kernel Threads at module unload time
    • From: "linux-os \(Dick Johnson\)" <[email protected]>

• Prev by Date: Re: XFS information leak during crash
• Next by Date: Re: [PATCH 1/39] NLKD - an alternative kallsyms approach
• Previous by thread: Re: Stopping Kernel Threads at module unload time
• Next by thread: Re: Stopping Kernel Threads at module unload time
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]