diff options
author | Jon Maloy <jon.maloy@ericsson.com> | 2017-12-21 16:36:34 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-12-26 21:06:36 +0300 |
commit | 3a33a19bf88cdfc6d982972bc6ffcf7a62c1015e (patch) | |
tree | 822156ba441ed4d0231d6a5dd54a283aabf5caf8 /include/trace | |
parent | 4853f128c13ed2731625dff2410b7fdbe540fb26 (diff) | |
download | linux-3a33a19bf88cdfc6d982972bc6ffcf7a62c1015e.tar.xz |
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>
Diffstat (limited to 'include/trace')
0 files changed, 0 insertions, 0 deletions