Make eht_cap != NULL check explicit to help static analyzers

data->eht_enabled was used to avoid getting here with eht_cap == NULL,
but that was too complex for some static analyzers. Make this more
explicit to avoid false reports.

Signed-off-by: Jouni Malinen <j@w1.fi>

diff --git a/src/common/hw_features_common.c b/src/common/hw_features_common.c
index 78a68aa87daef8b2a4acf185f49f3b03fd2715ca..d9276b93541efaeb17ff8fae4ca3e6abfe005c3e 100644 (file)
--- a/src/common/hw_features_common.c
+++ b/src/common/hw_features_common.c
@@ -594,7 +594,8 @@ int hostapd_set_freq_params(struct hostapd_freq_params *data,
 
        if (data->eht_enabled) switch (oper_chwidth) {
        case CONF_OPER_CHWIDTH_320MHZ:
-               if (!(eht_cap->phy_cap[EHT_PHYCAP_320MHZ_IN_6GHZ_SUPPORT_IDX] &
+               if (eht_cap &&
+                   !(eht_cap->phy_cap[EHT_PHYCAP_320MHZ_IN_6GHZ_SUPPORT_IDX] &
                      EHT_PHYCAP_320MHZ_IN_6GHZ_SUPPORT_MASK)) {
                        wpa_printf(MSG_ERROR,
                                   "320 MHz channel width is not supported in 5 or 6 GHz");