Bluetooth: When encryption is dropped, do not send RFCOMM packets
authorJaikumar Ganesh <jaikumar@google.com>
Tue, 3 Feb 2009 02:03:57 +0000 (18:03 -0800)
committerMarcel Holtmann <marcel@holtmann.org>
Fri, 27 Feb 2009 05:14:35 +0000 (06:14 +0100)
commit6e1031a40029492c10509e8c3dcac9b611438ccb
tree534b3b4c4b1495ae0f948453bf54e0d71e1216f5
parent34a55eda483e8177c9044f93fd2c9107f02bf1c7
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>
net/bluetooth/rfcomm/core.c