aboutsummaryrefslogtreecommitdiffstats
path: root/net/unix/af_unix.c
diff options
context:
space:
mode:
authorTejun Heo <[email protected]>2010-08-24 12:22:47 +0000
committerTejun Heo <[email protected]>2010-08-24 16:01:32 +0000
commite41e704bc4f49057fc68b643108366e6e6781aa3 (patch)
tree8cc85208970ba0c9adf533903243e28c506f23ae /net/unix/af_unix.c
parentworkqueue: mark lock acquisition on worker_maybe_bind_and_lock() (diff)
downloadkernel-e41e704bc4f49057fc68b643108366e6e6781aa3.tar.gz
kernel-e41e704bc4f49057fc68b643108366e6e6781aa3.zip
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 <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions