aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2019-09-23 11:08:58 -0700
committerTejun Heo <tj@kernel.org>2019-10-04 10:23:01 -0700
commitc29eb85386880750130a01aabf288408a6614d65 (patch)
treea1611859442a41355f2182432afb2bec93921d01 /tools/perf/util/scripting-engines/trace-event-python.c
parentworkqueue: Minor follow-ups to the rescuer destruction change (diff)
downloadwireguard-linux-c29eb85386880750130a01aabf288408a6614d65.tar.xz
wireguard-linux-c29eb85386880750130a01aabf288408a6614d65.zip
workqueue: more destroy_workqueue() fixes
destroy_workqueue() warnings still, at a lower frequency, trigger spuriously. The problem seems to be in-flight operations which haven't reached put_pwq() yet. * Make sanity check grab all the related locks so that it's synchronized against operations which puts pwq at the end. * Always print out the offending pwq. Signed-off-by: Tejun Heo <tj@kernel.org> Cc: "Williams, Gerald S" <gerald.s.williams@intel.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions