[PATCH] Bluetooth: When encryption is dropped, do not send RFCOMM tx packets.

[jaikumar Ganesh <jaikumarg@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 173 bytes --]

Hi Marcel,
    The patch for pausing RFCOMM tx traffic during the grace period
when the encryption is dropped (as a result of the role change) is
attached.

Thanks
Jaikumar

[-- Attachment #2: 0001-Bluetooth-When-encryption-is-dropped-do-not-send-R.patch --]
[-- Type: application/octet-stream, Size: 1101 bytes --]

From 42455699936fd3064044c3fe443e66cfea793ee1 Mon Sep 17 00:00:00 2001
From: Jaikumar Ganesh <jaikumar@google.com>
Date: Mon, 2 Feb 2009 18:03:57 -0800
Subject: [PATCH] Bluetooth: When encryption is dropped, do not send RFCOMM tx packets.

During a role change, the remote side drops the encryption of the RFCOMM
connection. We allow a grace period for the encryption to be reestablished,
before dropping the connection. During this grace period, the RFCOMM_SEC_PENDING
flag is set. Check this flag before sending RFCOMM tx packets.

Signed-off-by: Jaikumar Ganesh <jaikumar@google.com>
---
 net/bluetooth/rfcomm/core.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/net/bluetooth/rfcomm/core.c b/net/bluetooth/rfcomm/core.c
index ad0e25a..3717c25 100644
--- a/net/bluetooth/rfcomm/core.c
+++ b/net/bluetooth/rfcomm/core.c
@@ -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;
 
-- 
1.5.4.5