From: Tuong Lien <tuong.t.l...@dektech.com.au> Date: Mon, 4 May 2020 11:15:54 +0700
> When an application connects to the TIPC topology server and subscribes > to some services, a new connection is created along with some objects - > 'tipc_subscription' to store related data correspondingly... > However, there is one omission in the connection handling that when the > connection or application is orderly shutdown (e.g. via SIGQUIT, etc.), > the connection is not closed in kernel, the 'tipc_subscription' objects > are not freed too. > This results in: > - The maximum number of subscriptions (65535) will be reached soon, new > subscriptions will be rejected; > - TIPC module cannot be removed (unless the objects are somehow forced > to release first); > > The commit fixes the issue by closing the connection if the 'recvmsg()' > returns '0' i.e. when the peer is shutdown gracefully. It also includes > the other unexpected cases. > > Acked-by: Jon Maloy <jma...@redhat.com> > Acked-by: Ying Xue <ying....@windriver.com> > Signed-off-by: Tuong Lien <tuong.t.l...@dektech.com.au> Applied, thanks.
