summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorShay Drory <shayd@nvidia.com>2022-04-04 10:47:36 +0300
committerSaeed Mahameed <saeedm@nvidia.com>2022-05-18 09:03:57 +0300
commit16d42d313350946f4b9a8b74a13c99f0461a6572 (patch)
tree92f4be6fb52ef0fae981e152a47a2b3a8275b8f7 /tools/perf/scripts/python/export-to-sqlite.py
parent04c551bad3713661ac85902163b3a567864c9a7c (diff)
downloadlinux-16d42d313350946f4b9a8b74a13c99f0461a6572.tar.xz
net/mlx5: Drain fw_reset when removing device
In case fw sync reset is called in parallel to device removal, device might stuck in the following deadlock: CPU 0 CPU 1 ----- ----- remove_one uninit_one (locks intf_state_mutex) mlx5_sync_reset_now_event() work in fw_reset->wq. mlx5_enter_error_state() mutex_lock (intf_state_mutex) cleanup_once fw_reset_cleanup() destroy_workqueue(fw_reset->wq) Drain the fw_reset WQ, and make sure no new work is being queued, before entering uninit_one(). The Drain is done before devlink_unregister() since fw_reset, in some flows, is using devlink API devlink_remote_reload_actions_performed(). Fixes: 38b9f903f22b ("net/mlx5: Handle sync reset request event") Signed-off-by: Shay Drory <shayd@nvidia.com> Reviewed-by: Moshe Shemesh <moshe@nvidia.com> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions