From: Tejun Heo Date: Thu, 14 Mar 2013 02:47:39 +0000 (-0700) Subject: workqueue: better define locking rules around worker creation / destruction X-Git-Tag: omap-for-v3.10/dt-fixes-for-merge-window~125^2~40 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cd549687a7ee5e619a26f55af4059c4ae585811c;p=pandora-kernel.git workqueue: better define locking rules around worker creation / destruction When a manager creates or destroys workers, the operations are always done with the manager_mutex held; however, initial worker creation or worker destruction during pool release don't grab the mutex. They are still correct as initial worker creation doesn't require synchronization and grabbing manager_arb provides enough exclusion for pool release path. Still, let's make everyone follow the same rules for consistency and such that lockdep annotations can be added. Update create_and_start_worker() and put_unbound_pool() to grab manager_mutex around thread creation and destruction respectively and add lockdep assertions to create_worker() and destroy_worker(). This patch doesn't introduce any visible behavior changes. Signed-off-by: Tejun Heo --- Reading git-diff-tree failed