diff options
author | Parthasarathy Bhuvaragan <parthasarathy.bhuvaragan@ericsson.com> | 2017-01-24 13:00:45 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-01-24 16:14:57 -0500 |
commit | fc0adfc8fd18b61b6f7a3f28b429e134d6f3a008 (patch) | |
tree | 9080d3fca5d3fd7f654b16e290466c1ceb9b8a3f /tools/power | |
parent | d094c4d5f5c7e1b225e94227ca3f007be3adc4e8 (diff) | |
download | linux-fc0adfc8fd18b61b6f7a3f28b429e134d6f3a008.tar.bz2 |
tipc: fix connection refcount error
Until now, the generic server framework maintains the connection
id's per subscriber in server's conn_idr. At tipc_close_conn, we
remove the connection id from the server list, but the connection is
valid until we call the refcount cleanup. Hence we have a window
where the server allocates the same connection to an new subscriber
leading to inconsistent reference count. We have another refcount
warning we grab the refcount in tipc_conn_lookup() for connections
with flag with CF_CONNECTED not set. This usually occurs at shutdown
when the we stop the topology server and withdraw TIPC_CFG_SRV
publication thereby triggering a withdraw message to subscribers.
In this commit, we:
1. remove the connection from the server list at recount cleanup.
2. grab the refcount for a connection only if CF_CONNECTED is set.
Tested-by: John Thompson <thompa.atl@gmail.com>
Acked-by: Ying Xue <ying.xue@windriver.com>
Acked-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: Parthasarathy Bhuvaragan <parthasarathy.bhuvaragan@ericsson.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/power')
0 files changed, 0 insertions, 0 deletions