diff options
| author | Sowmini Varadhan <[email protected]> | 2017-11-30 11:11:29 -0800 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2017-12-01 15:25:15 -0500 |
| commit | f10b4cff98c6977668434fbf5dd58695eeca2897 (patch) | |
| tree | 71350054376a576a62bafac64b96b601f1290d85 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 681648e67d43cf269c5590ecf021ed481f4551fc (diff) | |
rds: tcp: atomically purge entries from rds_tcp_conn_list during netns delete
The rds_tcp_kill_sock() function parses the rds_tcp_conn_list
to find the rds_connection entries marked for deletion as part
of the netns deletion under the protection of the rds_tcp_conn_lock.
Since the rds_tcp_conn_list tracks rds_tcp_connections (which
have a 1:1 mapping with rds_conn_path), multiple tc entries in
the rds_tcp_conn_list will map to a single rds_connection, and will
be deleted as part of the rds_conn_destroy() operation that is
done outside the rds_tcp_conn_lock.
The rds_tcp_conn_list traversal done under the protection of
rds_tcp_conn_lock should not leave any doomed tc entries in
the list after the rds_tcp_conn_lock is released, else another
concurrently executiong netns delete (for a differnt netns) thread
may trip on these entries.
Reported-by: syzbot <[email protected]>
Signed-off-by: Sowmini Varadhan <[email protected]>
Acked-by: Santosh Shilimkar <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions