Change Ib55b211e4fdab427aff8c04c8ac99e1af56c6edc ("qcacld-3.0: Rename
pMac in csr_api_scan.c ") previously renamed all instances of pMac in
csr_api_scan.c to align with the Linux coding style.
Subsequently change Iac183da52495aca07c6270edeb9f383ab49c1ff5
("qcacld-3.0: Add CFG items of power") reintroduced pMac in function
csr_save_tx_power_to_cfg(), so once again rename it in that function.
Change-Id: I5272cf71c422618ae0e3c042a99f7728192321f2
CRs-Fixed: 2420015
In QCA_NL80211_VENDOR_SUBCMD_SET_TRACE_LEVEL command handler
when nested attributes are getting parsed no NLA policy is
used, as no NLA policy is defined for MODULE_ID and TRACE_MASK,
these attributes will be treated as NLA_UNSPEC types and can
have a length of zero bytes. Later when these attributes
are accessed using nla_get_u32() this will result in OOB
read.
Change-Id: I7d4913feccb00877ac5f40bab8ff5e9e3891756f
CRs-Fixed: 2410900
NON TX BSS may not respond to unicast probe request.
so dont send unicast probe request as part of association.
Change-Id: Ia36d71742e4632c6c979066a833bdc98b71bae9c
CRs-Fixed: 2415672
Mlme info is not updated for the new AP to which driver roamed and
also not updated for the old AP after driver roamed to new AP.
Also in some case when deauth is from peer the Mlme info is not reset
by driver for the disconnected AP.
As mlme info of the AP is not updated and it remain in associated state
The AGE out logic skip the AP and thus it never ageout.
Fix this by properly updating the MLME info of the AP during roaming
And disconnection.
Change-Id: Ib17499c8ab0c4725d146d7c09077c92661adbdd5
CRs-Fixed: 2419853
Currently, hdd_parse_vendor_acs_chan_config does not do null validation for
tb[SET_CHAN_CHAN_LIST] which can lead to null pointer derefrence.
Add null pointer check for tb[SET_CHAN_CHAN_LIST] in
hdd_parse_vendor_acs_chan_config.
Change-Id: I8914e38a5d98536a816c80d484dec9878753966a
CRs-Fixed: 2410809
The HDD driver operation inactivity timer has been rendered obsolete by
the addition and integration of the Driver Synchronization feature.
Remove the HDD driver operation inactivity timer.
Change-Id: I9c4f555f02edd9350cf44477c3ba6c84b61b09f7
CRs-Fixed: 2419307
Currently the driver just start the vdev according to the ini
params, without consdering the tx, rx chainmask supported by the
FW per band, per mac, which can lead to connection in 2x2, even
though FW is not capable of 2 antennas on a particular band.
Fix is to intersect both the tx, rx chainmask for both bands,
and change the ini to minimum of the nss supported by ini, and
the BDF setting of the chains.
Change-Id: Ib0e9bac19959bbcf9bade7dbd78674be4099a23d
CRs-Fixed: 2414103
Send MBSSID BSS information like profile number
and max profile count to firmware as part of VDEV
UP command.
Change-Id: I612f0be9c52fd61b25d1c884940f28ce9fe0872e
CRs-Fixed: 2399999
Monitor mode feature not required on SDXPRAIRIE, and disable
it to save memory.
Change-Id: I206ef4441cc64218cbdcea08aaa3ce584aa99bf0
CRs-Fixed: 2418590
The API's added in qal & qdf for abstracting the
OS calls are inlined and moved to the OS-specific
src directories.
Remove compilation of these specific files from qcacld Kbuild.
Change-Id: I0416ae721d4c86000672168da396966dd452363c
CRs-Fixed: 2418669
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within target_if replace any such comparisons with
logical operations performed on the pointer itself.
Change-Id: Id9b5185713b91b67ddf1d965a6c7e52508558d82
CRs-Fixed: 2418397
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier advertiseConcurrentOperation to be compliant.
Change-Id: I398a3a80caaafbb273a647b4c0b1f374db94d944
CRs-Fixed: 2418188
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier RSNMfpCapable to be compliant.
Change-Id: Ida5c11b7da71cd0f4b7a344ca5ddc1ab3975c840
CRs-Fixed: 2418185
In function tdls_delete_all_tdls_peers, bss peer can be NULL
if the bss peer is removed from vdev object. Hence, add NULL
check before getting its reference.
Change-Id: I9b2b03bc6db899c1c06de95ec5ee680d4b600aa7
CRs-Fixed: 2419567
Currently, whenever roaming is triggered after a successful roam scan
firmware sends a BTM query to current connected AP when it is 11v
capable. Driver completes roaming with candidates received as part of
BTM request from AP. STA respond to AP with BTM response after
successful initiation of roaming.
Now the requirement is FW could send "BTM query with a preferred
candidate list" after a successful roam scan for some roam scan reasons
like PER, LOW_RSSI, HIGH_RSSI, MAWC, DENSE etc. Preferred candidate list
is obtained as part of roam scan based on firmware bss scoring logic.
Add new ini "btm_query_bitmask" to configure the bitmask for roam scan
reasons which is sent to firmware as part of RSO start via wmi btm config
cmd. Fw sends "BTM query with preferred candidate list" only for those
roam scans which are enabled through this bitmask.
New INI: btm_query_bitmask
Min: 0
Max: 0xFFFFFFFF
Default: 0x8
Bitmask : 0x8 (LOW_RSSI) refer enum WMI_ROAM_TRIGGER_REASON_ID.
Change-Id: I24b538745f2ac88d4e5c990573234e0f8a881b1f
CRs-Fixed: 2408111
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within cmn_services replace any such comparisons with
logical operations performed on the pointer itself.
Change-Id: I7141cd900916bd4bbab1bc8c7a1b90589286582b
CRs-Fixed: 2418402
The Linux Coding Style frowns upon mixed-case names so rename HDD
identifier RSNMfpRequired to be compliant.
Change-Id: I9e4843c6ac8914580be5da668080802bdc0ec3c1
CRs-Fixed: 2418187
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within wma replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: I2b4125bc4ec229fbe466e6ce0ca4c3191f6cae59
CRs-Fixed: 2418387
Currently there is no support to configure the inactivity
timeout when driver goes to wow mode or when driver resumes
from wow mode.
Add support for PMO component to configure the wow mode
inactivity timeout with ini g_wow_data_inactivity_timeout
when driver enters into wow mode and when driver resumes
from wow mode add support to configure the inactivity
timeout for non wow mode with ini gDataInactivityTimeout.
CRs-fixed: 2412866
Change-Id: I0672f22a5dfec870e5e67b23058db2729b9a0848
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within mlme replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: Iac19509c5fdcce036e0288653d61638cf04f01d6
CRs-Fixed: 2418400
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within disa replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: Id25e4748819d206e361a55532a5ccfd648744b15
CRs-Fixed: 2418403
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within os_if replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: Ia316c656c5156960d254383a8de4bfc58522f877
CRs-Fixed: 2418386
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pMfpCapable to be
compliant.
Change-Id: I8431089e225736249f6427da4a22277e8ae962b6
CRs-Fixed: 2418186
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within p2p replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: I3f987cc2603bd3e4d41881db8c847046884d7e76
CRs-Fixed: 2418399
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within cds replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: Ib542e8e26c16dd0d6afccb0fd94bca75a89b21e1
CRs-Fixed: 2418395
Per the Linux Kernel coding style, as enforced by the kernel
checkpatch script, pointers should not be explicitly compared to
NULL. Therefore within bmi replace any such comparisons with logical
operations performed on the pointer itself.
Change-Id: I85578cf7e40e7d6c81246b423d5b626a9570c8b4
CRs-Fixed: 2418396
To avoid using qcacld code in cmn, when getting
wlan op mode, using op mode info from vdev rather
adapter.
Change-Id: If8432aae12800884e3a4567d99319afcdfa9d1f5
CRs-Fixed: 2412315
While processing vendor command acs_chan_config,
in hdd_parse_vendor_acs_chan_config() memory allocated for channel_list
is not de-allocated in error scenario. This leads to memory leak.
To address this, while returning error, free channel_list in
hdd_parse_vendor_acs_chan_config().
Change-Id: Icdd264cfaa2e4266c22bc87c234e4a21122618b6
CRs-Fixed: 2410875
While processing vendor command EXTERNAL_ACS,
in hdd_parse_vendor_acs_chan_config() total number of channels is
computed by parsing nested attribute ACS_CHANNEL_LIST.
Initially computed number of channels is stored in int data type and
later copied to u8 data type, this shall truncate if number of channels
is greater than 255.
Memory for channel list is allocated using truncated value but later
the same list is accessed using computed value which shall result in
buffer overflow.
To address this, validate computed value against MAX_CHANNELS.
Change-Id: Idbbf3b44fd238f7cff53bedd68f2c7627ecdfa9d
CRs-Fixed: 2410869
The Linux Coding Style frowns upon mixed-case names and so-called
Hungarian notation, so rename HDD identifier pMfpRequired to be
compliant.
Change-Id: I745e5773ce387744120081c8fa275e9255639152
CRs-Fixed: 2418184
lim_is_system_in_scan_state was used when scan was handled by host
and with scan offloaded the API always return false and thus is
of no use. Also the SCAN state used by it are never set.
Thus remove the unused scan state and lim_is_system_in_scan_state.
Change-Id: Ie9b78340035d85805cc9416f557b683a0a3be232
CRs-Fixed: 2417851
Currently, there are some attributes that dont have any NLA policy
specified. The absence of policy results the attribute to default to
NLA_UNSPEC. When handling this case in validate_nla() there is no
minimum length guarantee, meaning that the attribute can have zero
length. This will result in a one byte overread when calling
nla_get_u8().
To avoid this potential security vulnerability, add policy entry for the
attribute.
Change-Id: I19e5a032ccb2083d5f204be6ff7ac2f53aebf130
CRs-Fixed: 2408072
