[lkml]   [2006]   [Dec]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: workqueue deadlock

    * Andrew Morton <> wrote:

    > > > + if (cpu != -1)
    > > > + mutex_lock(&workqueue_mutex);
    > >
    > > events/4 thread itself wanting the same mutex above?
    > Could do, not sure. I'm planning on converting all the locking around
    > here to preempt_disable() though.

    please at least use an owner-recursive per-CPU lock, not a naked
    preempt_disable()! The concurrency rules for data structures changed via
    preempt_disable() are quite hard to sort out after the fact.
    (preempt_disable() is too opaque, it doesnt attach data structure to
    critical section, like normal locks do.)

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-12-09 11:31    [W:2.528 / U:0.356 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site