diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2020-12-09 14:03:31 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-12-10 06:31:58 +0300 |
| commit | d7b1bfd0832c1d005f571203306b6c50e9805150 (patch) | |
| tree | 4835210f79ccb092abb8aff17daecae4f21acd38 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 0597d0f8e030d1a5e64708b0f3233209a8b5d39e (diff) | |
| download | linux-d7b1bfd0832c1d005f571203306b6c50e9805150.tar.xz | |
mptcp: be careful on subflows shutdown
When the workqueue disposes of the msk, the subflows can still
receive some data from the peer after __mptcp_close_ssk()
completes.
The above could trigger a race between the msk receive path and the
msk destruction. Acquiring the mptcp_data_lock() in __mptcp_destroy_sock()
will not save the day: the rx path could be reached even after msk
destruction completes.
Instead use the subflow 'disposable' flag to prevent entering
the msk receive path after __mptcp_close_ssk().
Fixes: e16163b6e2b7 ("mptcp: refactor shutdown and close")
Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions