RDS: TCP: rds_tcp_accept_worker() must exit gracefully when terminating rds-tcp
authorSowmini Varadhan <sowmini.varadhan@oracle.com>
Wed, 18 May 2016 17:06:23 +0000 (10:06 -0700)
committerDavid S. Miller <davem@davemloft.net>
Fri, 20 May 2016 23:19:57 +0000 (19:19 -0400)
commit37e14f4fe2991f6089a9c8a3830e3ab634ec7190
treeae8fd4ac36094170b29eb6dc73027773b23c60ba
parentfc64869c48494a401b1fb627c9ecc4e6c1d74b0d
RDS: TCP: rds_tcp_accept_worker() must exit gracefully when terminating rds-tcp

There are two instances where we want to terminate RDS-TCP: when
exiting the netns or during module unload. In either case, the
termination sequence is to stop the listen socket, mark the
rtn->rds_tcp_listen_sock as null, and flush any accept workqs.
Thus any workqs that get flushed at this point will encounter a
null rds_tcp_listen_sock, and must exit gracefully to allow
the RDS-TCP termination to complete successfully.

Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/rds/tcp_listen.c