Commit 1b6fa141 authored Jul 17, 2020 by Venkata Jagadeesh Garaga

L2cap: Cancel Sm4 timeout after security complete

Issue:
stack rejecting incoming Profile connection if remote delayed
information responce

Steps:
Pre-condition:
===========
RD2 in paired list

1. Pair and connect RD1.
2. Initiate music streaming.
3. Power on RD2.

Actual Result:
DUT incoming profile connection with refused-PSM not supported to
incoming RD2 connection

Expected result:
Incoming connection from RD2 should be successful.

RootCause:
When DUT receives incoming connection from remote device, stack starts
Security manager timer.on security complete , stack restarts the timer
with channel connection timeout timer if information response received
from remote. But if any IOT remote takes more than 2 sec to give
information response , stack security timer expires and stack
rejecting incoming connection.

Stack should stop the security manager timeout after connection complete

Fix:
cancel Sm4 timeout after security complete

Test:
Verified with above steps

Bug: 161517455
Change-Id: Ib3de15d3b17f1e3eb832724e0bd9410fada45a46

parent 47c9e6d0

system/stack/l2cap/l2c_csm.cc

+6 −0

Original line number	Diff line number	Diff line
		@@ -440,6 +440,12 @@ static void l2c_csm_term_w4_sec_comp(tL2C_CCB* p_ccb, uint16_t event,
		** stack version : 05.04.11.20060119
		*/

		/* Cancel ccb timer as security complete. waiting for w4_info_rsp
		** once info rsp received, connection rsp timer will be started
		** while sending connection ind to profiles
		*/
		alarm_cancel(p_ccb->l2c_ccb_timer);

		/* Waiting for the info resp, tell the peer to set a longer timer */
		l2cu_send_peer_connect_rsp(p_ccb, L2CAP_CONN_PENDING, 0);
		}