tipc: Prevent broadcast link stalling in dual LAN environments
authorAllan Stephens <allan.stephens@windriver.com>
Tue, 25 Oct 2011 16:19:05 +0000 (12:19 -0400)
committerPaul Gortmaker <paul.gortmaker@windriver.com>
Mon, 6 Feb 2012 21:59:16 +0000 (16:59 -0500)
commit4d75313ce9b832efc4efb487f080b5ed72beae2c
tree801ae5a62e6b53624e526fb2236015f3b2ef7e15
parent92d2c905b404d8d056ce35a0ce645e23529742c2
tipc: Prevent broadcast link stalling in dual LAN environments

Ensure that sequence number information about incoming broadcast link
messages is initialized only by the activation of the first link to a
given cluster node.  Previously, a race condition allowed reset and/or
activation messages for a second link to re-initialize this sequence
number information with obsolete values. This could trigger TIPC to
request the retransmission of previously acknowledged broadcast link
messages from that node, resulting in broadcast link processing becoming
stalled if the node had already released one or more of those messages
and was unable to perform the required retransmission.

Thanks to Laser <gotolaser@gmail.com> for identifying this problem
and assisting in the development of this fix.

Signed-off-by: Allan Stephens <allan.stephens@windriver.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
net/tipc/link.c