[lkml]   [2009]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Add kerneldoc for flush_scheduled_work()
    On Tue, 2009-08-11 at 17:06 -0400, Alan Stern wrote:
    > This patch (as1279) adds kerneldoc for flush_scheduled_work()
    > containing a stern warning that the function should be avoided.
    > Signed-off-by: Alan Stern <>
    > ---
    > Index: usb-2.6/kernel/workqueue.c
    > ===================================================================
    > --- usb-2.6.orig/kernel/workqueue.c
    > +++ usb-2.6/kernel/workqueue.c
    > @@ -739,6 +739,24 @@ int schedule_on_each_cpu(work_func_t fun
    > return 0;
    > }
    > +/**
    > + * flush_scheduled_work - ensure that all work scheduled on keventd_wq has run to completion.
    > + *
    > + * Blocks until all works on the keventd_wq global workqueue have completed.
    > + * We sleep until all works present upon entry have been handled, but we
    > + * are not livelocked by new incoming ones.
    > + *
    > + * Use of this function is discouraged, as it is highly prone to deadlock.
    > + * It should never be called from within a work routine on the global
    > + * queue, and it should never be called while holding a mutex required
    > + * by one of the works on the global queue. But the fact that keventd_wq
    > + * _is_ global means that it can contain works requiring practically any
    > + * mutex. Hence this routine shouldn't be called while holding any mutex.

    I really don't see why this should be "discouraged". It has exactly the
    same entangled deadlock problems as a lot of other functions like

    > + * Consider using cancel_work_sync() or cancel_delayed_work_sync() instead.
    > + * They don't do the same thing (they cancel the work instead of waiting
    > + * for it to complete), but in most cases they will suffice.
    > + */

    And this is wrong advice. If you've violated the entangled deadlock
    rules, the cancel functions will deadlock on you as well if the work is
    still pending. The other problem is that cancellation is a completely
    different operation from flushing. Flush is usually used in driver
    shutdown routines to complete all outstanding tasks before going away.
    Cancel wouldn't really have the same effect since the tasks may never
    get done.

    The final problem with this is that it creates a dichotomy between this
    function, which is simply a wrapper for flush_workqueue() on the
    keventd_wq and flush_workqueue(). flush_workqueue() has no scary
    warnings, so are we trying to encourage driver writers all to create
    their own workqueues for everything and declaring the global kernel
    workqueue useless? Or are we saying flushing workqueues is always bad
    and we just haven't got around to updating the documentation on


     \ /
      Last update: 2009-08-12 16:05    [W:0.022 / U:12.548 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site