summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorJon Maloy <jon.maloy@ericsson.com>2017-12-18 17:34:16 +0100
committerDavid S. Miller <davem@davemloft.net>2017-12-18 13:16:40 -0500
commit234833991e14681f61cbfd93e65a5c976089cf11 (patch)
tree757e5c311799b033dc7bd0fe10d55e99931f3b4e /net
parentb36025b19a2301ba0cac05e6ffad5668013d2c77 (diff)
downloadlinux-234833991e14681f61cbfd93e65a5c976089cf11.tar.gz
linux-234833991e14681f61cbfd93e65a5c976089cf11.tar.bz2
linux-234833991e14681f61cbfd93e65a5c976089cf11.zip
tipc: fix lost member events bug
Group messages are not supposed to be returned to sender when the destination socket disappears. This is done correctly for regular traffic messages, by setting the 'dest_droppable' bit in the header. But we forget to do that in group protocol messages. This has the effect that such messages may sometimes bounce back to the sender, be perceived as a legitimate peer message, and wreak general havoc for the rest of the session. In particular, we have seen that a member in state LEAVING may go back to state RECLAIMED or REMITTED, hence causing suppression of an otherwise expected 'member down' event to the user. We fix this by setting the 'dest_droppable' bit even in group protocol messages. Signed-off-by: Jon Maloy <jon.maloy@ericsson.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
-rw-r--r--net/tipc/group.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/net/tipc/group.c b/net/tipc/group.c
index 95fec2c057d6..efb5714e7a85 100644
--- a/net/tipc/group.c
+++ b/net/tipc/group.c
@@ -648,6 +648,7 @@ static void tipc_group_proto_xmit(struct tipc_group *grp, struct tipc_member *m,
} else if (mtyp == GRP_REMIT_MSG) {
msg_set_grp_remitted(hdr, m->window);
}
+ msg_set_dest_droppable(hdr, true);
__skb_queue_tail(xmitq, skb);
}