tipc: Auto removal of peer down node instance
authorGhantaKrishnamurthy MohanKrishna <mohan.krishna.ghanta.krishnamurthy@ericsson.com>
Fri, 29 Jun 2018 11:23:41 +0000 (13:23 +0200)
committerDavid S. Miller <davem@davemloft.net>
Sat, 30 Jun 2018 12:05:23 +0000 (21:05 +0900)
commit6a939f365bdb03a74b4617bdb4402fc08da088b9
treeaa22caa509706d637c8d2f84304f86f9aa4c1c56
parente397286b8e89bf38f4f56c0dcf6626e79dc2a323
tipc: Auto removal of peer down node instance

A peer node is considered down if there are no
active links (or) lost contact to the node. In current implementation,
a peer node instance is deleted either if

a) TIPC module is removed (or)
b) Application can use a netlink/iproute2 interface to delete a
specific down node.

Thus, a down node instance lives in the system forever, unless the
application explicitly removes it.

We fix this by deleting the nodes which are down for
a specified amount of time (5 minutes).
Existing node supervision timer is used to achieve this.

Acked-by: Ying Xue <ying.xue@windriver.com>
Acked-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: GhantaKrishnamurthy MohanKrishna <mohan.krishna.ghanta.krishnamurthy@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/tipc/node.c