Jon Maloy 3a33a19bf8 tipc: fix memory leak of group member when peer node is lost
When a group member receives a member WITHDRAW event, this might have
two reasons: either the peer member is leaving the group, or the link
to the member's node has been lost.

In the latter case we need to issue a DOWN event to the user right away,
and let function tipc_group_filter_msg() perform delete of the member
item. However, in this case we miss to change the state of the member
item to MBR_LEAVING, so the member item is not deleted, and we have a
memory leak.

We now separate better between the four sub-cases of a WITHRAW event
and make sure that each case is handled correctly.

Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-12-26 13:06:36 -05:00
..
2015-05-14 12:24:45 -04:00
2017-10-13 08:46:00 -07:00
2015-03-05 22:08:42 -05:00
2017-11-03 15:48:46 +09:00
2016-07-26 14:26:42 -07:00
2017-10-26 09:38:34 +09:00
2016-08-18 23:36:07 -07:00
2017-08-23 22:31:38 -07:00
2017-10-13 08:46:00 -07:00
2017-12-13 13:44:36 -05:00