diff options
author | Matthieu Baerts (NGI0) <matttbe@kernel.org> | 2024-07-27 12:01:28 +0200 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2024-07-30 10:27:30 +0200 |
commit | 6834097fc38c5416701c793da94558cea49c0a1f (patch) | |
tree | 819f07d69be352b553b2ad9866e3d53abd2bc689 /LICENSES | |
parent | selftests: mptcp: join: validate backup in MPJ (diff) | |
download | linux-6834097fc38c5416701c793da94558cea49c0a1f.tar.xz linux-6834097fc38c5416701c793da94558cea49c0a1f.zip |
mptcp: pm: fix backup support in signal endpoints
There was a support for signal endpoints, but only when the endpoint's
flag was changed during a connection. If an endpoint with the signal and
backup was already present, the MP_JOIN reply was not containing the
backup flag as expected.
That's confusing to have this inconsistent behaviour. On the other hand,
the infrastructure to set the backup flag in the SYN + ACK + MP_JOIN was
already there, it was just never set before. Now when requesting the
local ID from the path-manager, the backup status is also requested.
Note that when the userspace PM is used, the backup flag can be set if
the local address was already used before with a backup flag, e.g. if
the address was announced with the 'backup' flag, or a subflow was
created with the 'backup' flag.
Fixes: 4596a2c1b7f5 ("mptcp: allow creating non-backup subflows")
Cc: stable@vger.kernel.org
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/507
Reviewed-by: Mat Martineau <martineau@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'LICENSES')
0 files changed, 0 insertions, 0 deletions