Tejun Heo e41e704bc4 workqueue: improve destroy_workqueue() debuggability
Now that the worklist is global, having works pending after wq
destruction can easily lead to oops and destroy_workqueue() have
several BUG_ON()s to catch these cases.  Unfortunately, BUG_ON()
doesn't tell much about how the work became pending after the final
flush_workqueue().

This patch adds WQ_DYING which is set before the final flush begins.
If a work is requested to be queued on a dying workqueue,
WARN_ON_ONCE() is triggered and the request is ignored.  This clearly
indicates which caller is trying to queue a work on a dying workqueue
and keeps the system working in most cases.

Locking rule comment is updated such that the 'I' rule includes
modifying the field from destruction path.

Signed-off-by: Tejun Heo <tj@kernel.org>
2010-08-24 18:01:32 +02:00
..
2010-07-29 13:24:57 +02:00
2010-08-12 08:43:30 -07:00
2010-08-09 16:48:42 -04:00
2010-07-14 11:29:46 +02:00
2010-07-28 09:58:19 -04:00
2010-08-11 00:28:20 -04:00
2010-08-09 20:45:02 -07:00
2010-06-29 10:07:09 +02:00
2010-05-19 08:18:44 +02:00
2010-08-11 23:04:20 +09:30
2010-05-11 12:01:10 -07:00
2010-07-16 09:48:48 +02:00
2010-07-27 12:40:54 +02:00
2010-03-06 11:26:23 -08:00
2010-05-10 08:48:39 +02:00