Bluetooth: When encryption is dropped, do not send RFCOMM packets
During a role change with pre-Bluetooth 2.1 devices, the remote side drops the encryption of the RFCOMM connection. We allow a grace period for the encryption to be re-established, before dropping the connection. During this grace period, the RFCOMM_SEC_PENDING flag is set. Check this flag before sending RFCOMM packets. Signed-off-by: Jaikumar Ganesh <jaikumar@google.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
parent
34a55eda48
commit
6e1031a400
|
@ -1749,6 +1749,9 @@ static inline void rfcomm_process_dlcs(struct rfcomm_session *s)
|
|||
continue;
|
||||
}
|
||||
|
||||
if (test_bit(RFCOMM_SEC_PENDING, &d->flags))
|
||||
continue;
|
||||
|
||||
if (test_bit(RFCOMM_TX_THROTTLED, &s->flags))
|
||||
continue;
|
||||
|
||||
|
|
Loading…
Reference in New Issue