This is a note to let you know that I've just added the patch titled
Bluetooth: 6lowpan: Increase the connection timeout value
to the 3.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
bluetooth-6lowpan-increase-the-connection-timeout-value.patch
and it can be found in the queue-3.17 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 2ae50d8d3aaf7154f72b44331b71f15799cdc1bb Mon Sep 17 00:00:00 2001
From: Jukka Rissanen <jukka.rissanen@xxxxxxxxxxxxxxx>
Date: Mon, 8 Sep 2014 12:11:43 +0300
Subject: Bluetooth: 6lowpan: Increase the connection timeout value
From: Jukka Rissanen <jukka.rissanen@xxxxxxxxxxxxxxx>
commit 2ae50d8d3aaf7154f72b44331b71f15799cdc1bb upstream.
Use the default connection timeout value defined in l2cap.h because
the current timeout was too short and most of the time the connection
attempts timed out.
Signed-off-by: Jukka Rissanen <jukka.rissanen@xxxxxxxxxxxxxxx>
Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
net/bluetooth/6lowpan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/net/bluetooth/6lowpan.c
+++ b/net/bluetooth/6lowpan.c
@@ -890,7 +890,7 @@ static void chan_resume_cb(struct l2cap_
static long chan_get_sndtimeo_cb(struct l2cap_chan *chan)
{
- return msecs_to_jiffies(1000);
+ return L2CAP_CONN_TIMEOUT;
}
static const struct l2cap_ops bt_6lowpan_chan_ops = {
Patches currently in stable-queue which might be from jukka.rissanen@xxxxxxxxxxxxxxx are
queue-3.17/bluetooth-6lowpan-set-the-peer-ipv6-address-correctly.patch
queue-3.17/bluetooth-6lowpan-increase-the-connection-timeout-value.patch
queue-3.17/bluetooth-6lowpan-route-packets-that-are-not-meant-to-peer-via-correct-device.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html