提交 9ae26027 编写于 作者: O Oleg Nesterov 提交者: Linus Torvalds

update the comment in kthread_stop()

Commit 63706172 ("kthreads: rework
kthread_stop()") removed the limitation that the thread function mysr
not call do_exit() itself, but forgot to update the comment.

Since that commit it is OK to use kthread_stop() even if kthread can
exit itself.
Signed-off-by: NOleg Nesterov <oleg@redhat.com>
Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
上级 6560dc16
...@@ -180,10 +180,12 @@ EXPORT_SYMBOL(kthread_bind); ...@@ -180,10 +180,12 @@ EXPORT_SYMBOL(kthread_bind);
* @k: thread created by kthread_create(). * @k: thread created by kthread_create().
* *
* Sets kthread_should_stop() for @k to return true, wakes it, and * Sets kthread_should_stop() for @k to return true, wakes it, and
* waits for it to exit. Your threadfn() must not call do_exit() * waits for it to exit. This can also be called after kthread_create()
* itself if you use this function! This can also be called after * instead of calling wake_up_process(): the thread will exit without
* kthread_create() instead of calling wake_up_process(): the thread * calling threadfn().
* will exit without calling threadfn(). *
* If threadfn() may call do_exit() itself, the caller must ensure
* task_struct can't go away.
* *
* Returns the result of threadfn(), or %-EINTR if wake_up_process() * Returns the result of threadfn(), or %-EINTR if wake_up_process()
* was never called. * was never called.
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册