tipc: fix a link reset issue due to retransmission failures
authorYing Xue <ying.xue@windriver.com>
Wed, 25 Mar 2015 10:09:40 +0000 (18:09 +0800)
committerDavid S. Miller <davem@davemloft.net>
Wed, 25 Mar 2015 15:43:32 +0000 (11:43 -0400)
commitbc14b8d6a98eb0747126cd517b468148b9e1c7ac
tree188f60c5051b38a7d32a072b88c90767b5f39f91
parent358e048d670a0feeb030effd1a3611cc6288fa70
tipc: fix a link reset issue due to retransmission failures

When a node joins a cluster while we are transmitting a fragment
stream over the broadcast link, it's missing the preceding fragments
needed to build a meaningful message. As a result, the node has to
drop it. However, as the fragment message is not acknowledged to
its sender before it's dropped, it accidentally causes link reset
of retransmission failure on the node.

Reported-by: Erik Hugne <erik.hugne@ericsson.com>
Signed-off-by: Ying Xue <ying.xue@windriver.com>
Reviewed-by: Erik Hugne <erik.hugne@ericsson.com>
Tested-by: Erik Hugne <erik.hugne@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/tipc/bcast.c