Query: flush_scheduled_work
OS: centos
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
FLUSH_SCHEDULED_WORK(9) Driver Basics FLUSH_SCHEDULED_WORK(9)NAMEflush_scheduled_work - ensure that any scheduled work has run to completion.SYNOPSISvoid flush_scheduled_work(void);ARGUMENTSvoid no argumentsDESCRIPTIONForces 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 situationsWILL LEAD TO DEADLOCKOne 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.COPYRIGHTKernel Hackers Manual 3.10 June 2014 FLUSH_SCHEDULED_WORK(9)
Related Man Pages |
---|
device_schedule_callback_owner(9) - centos |
sysmon_task_queue_fini(9) - netbsd |
sysmon_task_queue_init(9) - netbsd |
workqueue_enqueue(9) - netbsd |
tapset::irq(3stap) - centos |
Similar Topics in the Unix Linux Community |
---|
Weird 'find' results |
Set hard block limit for user using quota |
DB2 convert digits to binary format |
Shopt -s histappend |
Controlling user input |