iwlwifi: mvm: check time-event vif to avoid bad deletion
The time event is initialized relatively late in interface (mvmvif) initialization, so it's possible to fail before that happens. As a consequence, the driver will crash if it ever tries to delete this time event in case initialization was unsuccessful. Avoid this by using the time event's vif pointer to indicate validity. The vif pointer is != NULL whenever the id is != TE_MAX, except for this special error case where the vif pointer will have the correct property (as the whole memory is cleared on allocation) whereas the id is 0, causing a crash in trying to delete the time event from the list. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
This commit is contained in:
parent
f9e5554cd8
commit
00fd233ac4
|
@ -86,7 +86,7 @@ void iwl_mvm_te_clear_data(struct iwl_mvm *mvm,
|
|||
{
|
||||
lockdep_assert_held(&mvm->time_event_lock);
|
||||
|
||||
if (te_data->id == TE_MAX)
|
||||
if (!te_data->vif)
|
||||
return;
|
||||
|
||||
list_del(&te_data->list);
|
||||
|
|
Loading…
Reference in New Issue