diff options
| author |   Miri Korenblit <miriam.rachel.korenblit@intel.com> | 2025-04-23 09:16:37 +0300 |
|---|---|---|
| committer |   Johannes Berg <johannes.berg@intel.com> | 2025-04-23 15:37:40 +0200 |
| commit | b68df31ce636f397098ff426348d4e976d343404 (patch) | |
| tree | 065d605fffdf2982186483fc178dacaad32e529c /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | wifi: iwlwifi: mld: refactor purging async notifications (diff) | |
| download | wireguard-linux-b68df31ce636f397098ff426348d4e976d343404.tar.xz wireguard-linux-b68df31ce636f397098ff426348d4e976d343404.zip | |
wifi: iwlwifi: mld: properly handle async notification in op mode start
From the moment that we have ALIVE, we can receive notification that
are handled asynchronously.
Some notifications (for example iwl_rfi_support_notif) requires an
operational FW. So we need to make sure that they were handled in
iwl_op_mode_mld_start before we stop the FW. Flush the async_handlers_wk
there to achieve that.
Also, if loading the FW in op mode start failed, we need to cancel
these notifications, as they are from a dead FW.
More than that, not doing so can cause us to access freed memory
if async_handlers_wk is executed after ieee80211_free_hw is called.
Fix this by canceling all async notifications if a failure occurred in
init (after ALIVE).
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Johannes Berg <johannes.berg@intel.com>
Link: https://patch.msgid.link/20250423091408.a8f63d983466.Ifd77d9c1a29fdd278b0a7bfc2709dd5d5e5efdb1@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions