summaryrefslogtreecommitdiffstats
path: root/net/bluetooth
diff options
context:
space:
mode:
authorParthasarathy Bhuvaragan <parthasarathy.bhuvaragan@ericsson.com>2016-09-01 16:22:16 +0200
committerDavid S. Miller <davem@davemloft.net>2016-09-01 10:12:26 -0700
commitd2f394dc4816b7bd1b44981d83509f18f19c53f0 (patch)
tree1e9d3b4ccf3851afa51b45f505da13879044cfeb /net/bluetooth
parentaabdd09d535073c35f746e46c3a5d3286088be3a (diff)
downloadblackbird-obmc-linux-d2f394dc4816b7bd1b44981d83509f18f19c53f0.tar.gz
blackbird-obmc-linux-d2f394dc4816b7bd1b44981d83509f18f19c53f0.zip
tipc: fix random link resets while adding a second bearer
In a dual bearer configuration, if the second tipc link becomes active while the first link still has pending nametable "bulk" updates, it randomly leads to reset of the second link. When a link is established, the function named_distribute(), fills the skb based on node mtu (allows room for TUNNEL_PROTOCOL) with NAME_DISTRIBUTOR message for each PUBLICATION. However, the function named_distribute() allocates the buffer by increasing the node mtu by INT_H_SIZE (to insert NAME_DISTRIBUTOR). This consumes the space allocated for TUNNEL_PROTOCOL. When establishing the second link, the link shall tunnel all the messages in the first link queue including the "bulk" update. As size of the NAME_DISTRIBUTOR messages while tunnelling, exceeds the link mtu the transmission fails (-EMSGSIZE). Thus, the synch point based on the message count of the tunnel packets is never reached leading to link timeout. In this commit, we adjust the size of name distributor message so that they can be tunnelled. Reviewed-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: Parthasarathy Bhuvaragan <parthasarathy.bhuvaragan@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud