diff options
author | Jakub Kicinski <kuba@kernel.org> | 2025-01-14 13:32:13 -0800 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2025-01-14 13:32:14 -0800 |
commit | 9de1280fb5034a56f8827a521dec259982298581 (patch) | |
tree | 5206b860acabad5b957a809038b4af4d3becbf68 /scripts/gdb/linux/timerlist.py | |
parent | 665bcfc982deef247016a9ff679cdf45ae37162c (diff) | |
parent | 218cc166321fb3cc8786677ffe0d09a78778a910 (diff) |
Merge branch 'mptcp-fixes-for-connect-selftest-flakes'
Matthieu Baerts says:
====================
mptcp: fixes for connect selftest flakes
Last week, Jakub reported [1] that the MPTCP Connect selftest was
unstable. It looked like it started after the introduction of some fixes
[2]. After analysis from Paolo, these patches revealed existing bugs,
that should be fixed by the following patches.
- Patch 1: Make sure ACK are sent when MPTCP-level window re-opens. In
some corner cases, the other peer was not notified when more data
could be sent. A fix for v5.11, but depending on a feature introduced
in v5.19.
- Patch 2: Fix spurious wake-up under memory pressure. In this
situation, the userspace could be invited to read data not being there
yet. A fix for v6.7.
- Patch 3: Fix a false positive error when running the MPTCP Connect
selftest with the "disconnect" cases. The userspace could disconnect
the socket too soon, which would reset (MP_FASTCLOSE) the connection,
interpreted as an error by the test. A fix for v5.17.
Link: https://lore.kernel.org/20250107131845.5e5de3c5@kernel.org [1]
Link: https://lore.kernel.org/20241230-net-mptcp-rbuf-fixes-v1-0-8608af434ceb@kernel.org [2]
====================
Link: https://patch.msgid.link/20250113-net-mptcp-connect-st-flakes-v1-0-0d986ee7b1b6@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/timerlist.py')
0 files changed, 0 insertions, 0 deletions