From: Jon Maloy <[email protected]> Date: Mon, 18 Dec 2017 17:34:16 +0100
> 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 <[email protected]> Applied. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
