|author||Lai Jiangshan <firstname.lastname@example.org>||2015-05-20 14:41:19 +0800|
|committer||Tejun Heo <email@example.com>||2015-05-21 17:26:22 -0400|
workqueue: move flush_scheduled_work() to workqueue.h
flush_scheduled_work() is just a simple call to flush_work(). Signed-off-by: Lai Jiangshan <firstname.lastname@example.org> Signed-off-by: Tejun Heo <email@example.com>
Diffstat (limited to 'kernel/workqueue.c')
1 files changed, 0 insertions, 30 deletions
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index ad8dc2b9efc3..c9eaa4e5c867 100644
@@ -2959,36 +2959,6 @@ int schedule_on_each_cpu(work_func_t func)
- * flush_scheduled_work - ensure that any scheduled work has run to completion.
- * Forces execution of the kernel-global workqueue and blocks until its
- * completion.
- * Think twice before calling this function! It's very easy to get into
- * trouble if you don't take great care. Either of the following situations
- * will lead to deadlock:
- * One of the work items currently on the workqueue needs to acquire
- * a lock held by your code or its caller.
- * Your code is running in the context of a work routine.
- * They will be detected by lockdep when they occur, but the first might not
- * occur very often. It depends on what work items are on the workqueue and
- * what locks they need, which you have no control over.
- * In most situations flushing the entire workqueue is overkill; you merely
- * need to know that a particular work item isn't queued and isn't running.
- * In such cases you should use cancel_delayed_work_sync() or
- * cancel_work_sync() instead.
* execute_in_process_context - reliably execute the routine with user context
* @fn: the function to execute
* @ew: guaranteed storage for the execute work structure (must