aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorJon Paul Maloy <jon.maloy@ericsson.com>2015-03-09 16:16:22 -0400
committerDavid S. Miller <davem@davemloft.net>2015-03-09 16:20:41 -0400
commite6441bae326271090755e1707196ad05aa1dc703 (patch)
tree8114a09237def99e37033707b02e8019ca18264c /Documentation
parentnet: delete stale packet_mclist entries (diff)
downloadlinux-dev-e6441bae326271090755e1707196ad05aa1dc703.tar.xz
linux-dev-e6441bae326271090755e1707196ad05aa1dc703.zip
tipc: fix bug in link failover handling
In commit c637c1035534867b85b78b453c38c495b58e2c5a ("tipc: resolve race problem at unicast message reception") we introduced a new mechanism for delivering buffers upwards from link to socket layer. That code contains a bug in how we handle the new link input queue during failover. When a link is reset, some of its users may be blocked because of congestion, and in order to resolve this, we add any pending wakeup pseudo messages to the link's input queue, and deliver them to the socket. This misses the case where the other, remaining link also may have congested users. Currently, the owner node's reference to the remaining link's input queue is unconditionally overwritten by the reset link's input queue. This has the effect that wakeup events from the remaining link may be unduely delayed (but not lost) for a potentially long period. We fix this by adding the pending events from the reset link to the input queue that is currently referenced by the node, whichever one it is. This commit should be applied to both net and net-next. Signed-off-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions