summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/drivers/net/lib/py/env.py
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2025-02-18 21:36:14 +0300
committerJakub Kicinski <kuba@kernel.org>2025-02-20 06:05:28 +0300
commitbc68b0efa1bf923cef1294a631d8e7416c7e06e4 (patch)
tree10b11892c5f0e98e48e9e55cdf26ee7f809431a0 /tools/testing/selftests/drivers/net/lib/py/env.py
parentf03afb3aeb9d81f6c5ab728a61a040012923e3b3 (diff)
downloadlinux-bc68b0efa1bf923cef1294a631d8e7416c7e06e4.tar.xz
mptcp: move the whole rx path under msk socket lock protection
After commit c2e6048fa1cf ("mptcp: fix race in release_cb") we can move the whole MPTCP rx path under the socket lock leveraging the release_cb. We can drop a bunch of spin_lock pairs in the receive functions, use a single receive queue and invoke __mptcp_move_skbs only when subflows ask for it. This will allow more cleanup in the next patch. Some changes are worth specific mention: The msk rcvbuf update now always happens under both the msk and the subflow socket lock: we can drop a bunch of ONCE annotation and consolidate the checks. When the skbs move is delayed at msk release callback time, even the msk rcvbuf update is delayed; additionally take care of such action in __mptcp_move_skbs(). Signed-off-by: Paolo Abeni <pabeni@redhat.com> Reviewed-by: Mat Martineau <martineau@kernel.org> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org> Link: https://patch.msgid.link/20250218-net-next-mptcp-rx-path-refactor-v1-3-4a47d90d7998@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/testing/selftests/drivers/net/lib/py/env.py')
0 files changed, 0 insertions, 0 deletions