A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-12 07:37:31 -04:00
Code Issues Projects Releases Packages Wiki Activity

qcacld-3.0: Send failure reassoc response up on receiving reassoc req

Browse source 
SAP-DUT should reject reassoc request coming from STA to avoid
IOT issue.

Change-Id: I9f8080b6882053a24ac1cb16001b2ec7ceb54c12
CRs-Fixed: 2088722
This commit is contained in:
Krunal Soni 2017-06-07 16:42:38 -07:00 • committed by snandini
commit 17184269de
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
core/mac/src/pe/lim/lim_process_assoc_req_frame.c
View file

@ -1773,6 +1773,20 @@ void lim_process_assoc_req_frame(tpAniSirGlobal mac_ctx, uint8_t *rx_pkt_info,
sub_type, GET_LIM_SYSTEM_ROLE(session),
MAC_ADDR_ARRAY(hdr->sa));
return;
} else if (!sta_ds->rmfEnabled && (sub_type == LIM_REASSOC)) {
/*
* SAP should send reassoc response with reject code
* to avoid IOT issues. as per the specification SAP
* should do 4-way handshake after reassoc response and
* some STA doesn't like 4way handshake after reassoc
* where some STA does expect 4-way handshake.
*/
lim_send_assoc_rsp_mgmt_frame(mac_ctx,
eSIR_MAC_OUTSIDE_SCOPE_OF_SPEC_STATUS,
sta_ds->assocId, sta_ds->staAddr,
sub_type, sta_ds, session);
pe_err("Rejecting reassoc req from STA");
return;
} else if (!sta_ds->rmfEnabled) {
/*
* Do this only for non PMF case.