Currently FISA flows are added for packets received
from DNS server. The connection to DNS server are short
exchanges to resolve any URL, hence there is no need
to create FISA flows for such short lived flows.
Bypass FISA for packets from DNS server.
Change-Id: Ifd4f15f2c0b131148ccff7fd450d536ac029788d
CRs-Fixed: 3249810
Currently if SAP is up on 5 GHz DFS/non-DFS channel and country
change happens to world mode where SAP is not allowed on 5 GHz
channels then it moves to a 2.4 GHz channel and saves current
operating frequency band information, now again if a country
change happens SAP tries to move back to any allowed 5 GHz
DFS/non-DFS channel.
Sap should come to non-DFS channel first. If not available then
it should come on DFS channel
To address this issue, add a fix to check for first valid 5 GHz
non-DFS channel and first valid 5 GHz DFS channel. Move to
valid 5 GHz non-DFS channel if present.
Change-Id: I0cf3841e35e22efc0f518ce15b4cab40996cc645
CRs-Fixed: 3247522
Add change for WAPI IE in probe response introduced by
change : I9212e0fe9d495e8300a2bfbed65d398e0fb27170
and also add change to print mac address while
updating mac from old mac address to new mac address.
Change-Id: I6481b211fa26c540b079d119070cc2f1cc1d3abf
CRs-Fixed: 3249823
Currently the handler which dumps FISA stats, does not
check if the FISA feature has been enabled/disabled via
the INI. Accessing FST table when FISA has been disabled
via INI leads to unexpected assertion.
Fix this by checking if the FISA feature has been enabled
via INI, before accessing the FST table.
Change-Id: I5345138c5af03e3dd777bfe36004c477cff0ab7d
CRs-Fixed: 3249827
Currently, while we request netdev stats
we use the MAC address to find the DP interface.
There is a possibility that while we are
passing mac address to find DP interface
in parallel dynamic MAC update can happen
which will cause MAC address mismatch,
which will result in the DP interface not found
issue.
To fix the issue, instead of MAC address use
netdev name to search DP interface from
the list of available DP interface.
Change-Id: Ib04ce2fc7193be4733b16707600a10d3d729813c
CRs-Fixed: 3247725
Currently host driver does not update connected APs beacon
IE and because of this host is not able to pass this information
to userspace when it request for this info.
To address above issue, update connected APs beacon IE
correclty in host driver.
Change-Id: Id08d0162704883ad8ccb0f1c436aa8f9886f28c6
CRs-Fixed: 3193823
Firmware aborts the ongoing scan upon receiving new scan
channel list (through WMI_SCAN_CHAN_LIST_CMDID). Channel list
might get updated from userspace through commands like
country code change, power level change(SET_FCC_CHANNEL),...
It affects the features that are dependent on that scan,
e.g. ongoing connection, p2p find, etc.. Few frames might
be stuck in firmware as the scan is canceled.
It's recommended to defer the scan channel list update till
the current scan is done. This is already supported and
guarded through the ini param enable_pending_list_req
but disabled by default.
Enable the ini param to make sure above scenarios are not
affected due to channel list update.
Change-Id: I4176bb6a03657cf32f0c099b72254d61207ea6ca
CRs-Fixed: 3250137
Idle roam inactive time is expected in seconds but
the host driver is sending it in milliseconds, this causes
idle roam trigger not happening at the target.
Send the idle roam inactive time in seconds instead of
milliseconds.
Change-Id: If326a4bf464164183fdcd9baea9002483053adf7
CRs-Fixed: 3246541
Dedicated Bluetooth Antenna Mode (DBAM) feature is dependent
on COEX feature. So, enable CONFIG_FETURE_COEX in kiwi_v2
default config.
Change-Id: I1a2001f7be88d7527de5402d5272799b207a0077
CRs-Fixed: 3251103
Currently, in host driver, if ucfg_dp_init_tx_rx fails, it returns
error and this error is handled in hdd_init_nan_data_mode by
unregister the wext and detroying the vdev.
But wext unregister fails as it is waiting for rtnl_lock forever
which causes CPU to struck there.
To fix this, add rtnl held flag which will check rtln lock is
supported or not.
Change-Id: Ibc826ace63919979d743f6c8fcc26f1438d25274
CRs-Fixed: 3248716
Add assoc link bit in mlo_support_link_band to indicate supported band of
assoc link.
bit4: 2 GHz
bit5: 5 GHz
bit6: 6 GHz
Change-Id: I8fa156f43656ba91b8622ce12034ddad0bcf28a2
CRs-Fixed: 3250252
Currently In os_if_monitor_mode_configure API,
tb attribute is getting accessed before parsing
the data coming from userspace.
This is leading to illegal memory access.
Move tb attribute access after parsing userspace
data with API wlan_cfg80211_nla_parse.
Change-Id: Ia972ebb87e18ed82c6c3a2ff3ce2d10a4b9685b9
CRs-Fixed: 3241952
For the below GET driver command, print the value
before sending it to user space to enhance automation
tools:
1. GETDWELLTIME for 2 GHz, 5 GHz and 6 GHz channels
2. GETSCANCHANNELTIME
3. GETSCANHOMETIME
Change-Id: I8d090898828049107d4a00bbc3622665aa0e30ac
CRs-Fixed: 3247541
For 11BE mode, channel width information may be set in EHT
operation IE, and 11BE sta should populate its channel width
information in HE capabilities IE after extracting EHT operation IE.
Otherwise 11BE sta can't sends correct bandwidth information
to 11BE AP.
Change-Id: I08b4b61ad21017fde52d504f6d3e5c9b1e948950
CRs-Fixed: 3246725
AP/peer may send DELBA continuously in some error scenarios.
Host driver generates a dump of the frame in INFO level
and a log in ERROR level for each DELBA received. This
results in excessive logs to the kernel logging.
Rate limit the logs to avoid spamming kernel logs.
Change-Id: I94b11b76b862924672e06520b5bf2e731ec462df
CRs-Fixed: 3248606
Display control pipes info on WOW ack failure which helps to
debug issues when full debug history is not available.
Change-Id: I6a84aa01c07831b7109d0741337cae6ac0be2f44
CRs-Fixed: 3246284
Currently host does not check the return value of
hdd_process_peer_chain_rssi_req, returns success
on error case as well in __wlan_hdd_cfg80211_get_chain_rssi.
Also double conversion of qdf status to os_if status
is taking place which is giving wrong error status.
Remove extra status conversion and consider the return value
of hdd_process_peer_chain_rssi_req.
Change-Id: I387a36afe80eb4e7aa5bad746074d077b20de331
CRs-Fixed: 3245972
Add all members of csr_roamstart_bssparams structure to
parent structure and remove csr_roamstart_bssparams structure
Change-Id: Ifa9f38305e72de45776d6ead25a7053063792382
CRs-Fixed: 3247189
The AP rejects the FILS-IM association request with reason
"Invalid IE format". In the assoc request, two problems are
seen:
1. The RSN IE has a junk group management cipher suite.
2. FILS HLP container IE is fragmented, and the fragment
IE does not immediately follow the HLP container IE.
In the assoc request, the RSN IE encoded in the authentication
is unpacked and the PMKID is replaced with the pmkr1 name
derived at the end of FILS authentication. Currently, the
existing PMKID in the RSN IE is replaced only if the group
management cipher is present. In non-802.11w case, the new
PMKID is appended at the end of existing PMKID, and leads to
improper IE format.
To fix this, replace the existing PMKID whenever PMKID is
present.
To fix invalid HLP container IE format, encode the HLP
container and its fragment IEs together in the assoc request.
Also, inorder to get the pmksa match from the crypto table for
a FT-FILS, fill both ssid and cache ID. Without cache id, the
cached entry is not updated with MDIE.
Change-Id: I654b5527a726eb7872b90fb19a3d97623f3caa68
CRs-Fixed: 3233081
Currently for big data stats, driver stores correct rssi
value in cache_conn_info. But since vdev is in disconnected
state and unified_ll_stats_get_sta command is queried periodically
for every 3 seconds, firmware will now return 0 as a new rssi value.
The correct rssi value which is stored in cache_conn_info now
gets overwritten in hdd_lost_link_cp_stats_info_cb.
To avoid this issue, do not overwrite the rssi value for
big data stats if the rssi value returned by firmware is 0.
Change-Id: Iee0dba113d6ed684c00230a2714744191bcd0f7f
CRs-Fixed: 3248245
Correct description of ratemask_set ini for VHT mode
to avoid wrong configuration.
Change-Id: I91b887d8268f8faa0d0c32f90da032d00eaa14f2
CRs-Fixed: 3198950
In ath_pktlog_hdr, uint32_t type_specific_data member is
required for the framework while parsing with structure
type wh_pktlog_hdr_v2_t and without this member leads to
crash in userspace.
wifi hal expects "status" variable which is inside struct
packet_dump to be of "tx_pkt_fate" enum and any value
other than this will cause a tombstone crash.
As sizeof (struct ath_pktlog_hdr) is different in driver
and wifi hal, if PKTLOG_HAS_SPECIFIC_DATA is not enabled
then "status" is not decoded at correct offset which
causes the crash
So, feature flag PKTLOG_HAS_SPECIFIC_DATA is made available
globally to avoid crashes in userspace.
Change-Id: Ie6aca4bbcb5795595945cc4470162ab32c9c6734
CRs-Fixed: 3241071
In target_if_get_roam_vendor_control_param_event_handler,
there are 2 possible NULL pointer dereference issues:
1. Host calls target_if_get_psoc_from_scn_hdl API to get
psoc object. But as per current logic even if psoc is
NULL, psoc is dereferenced by passing it as an argument
to get_wmi_unified_hdl_from_psoc.
2. Host calls get_wmi_unified_hdl_from_psoc API to get
wmi_handle pointer. But as per current logic even if
wmi_handle is NULL, wmi_handle is dereferenced by
passing is as an argument 1 to function
wmi_extract_roam_vendor_control_param_event.
Fix is to update the sanity check logic for psoc and
wmi_handle pointers to avoid possible NULL pointer
dereference.
Change-Id: I3c3df062b538b05218e729d7bf6806e221073269
CRs-Fixed: 3242435
Restrict BW for TDLS when connection is made
in 2.4 GHz to that of AP.
Also, restrict the BW if the TDLS connection
is made in DFS channel.
Change-Id: Ida8693837b4b8e11a706b5b9fa482399630d2beb
CRs-Fixed: 3246100
