Commit dce1c6d
mptcp: pm: reset MPC endp ID when re-added
The initial subflow has a special local ID: 0. It is specific per
connection.
When a global endpoint is deleted and re-added later, it can have a
different ID -- most services managing the endpoints automatically don't
force the ID to be the same as before. It is then important to track
these modifications to be consistent with the ID being used for the
address used by the initial subflow, not to confuse the other peer or to
send the ID 0 for the wrong address.
Now when removing an endpoint, msk->mpc_endpoint_id is reset if it
corresponds to this endpoint. When adding a new endpoint, the same
variable is updated if the address match the one of the initial subflow.
Fixes: 3ad14f5 ("mptcp: more accurate MPC endpoint tracking")
Cc: stable@vger.kernel.org
Reviewed-by: Mat Martineau <martineau@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>1 parent bc19ff5 commit dce1c6d
1 file changed
Lines changed: 11 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1318 | 1318 | | |
1319 | 1319 | | |
1320 | 1320 | | |
1321 | | - | |
| 1321 | + | |
| 1322 | + | |
1322 | 1323 | | |
1323 | 1324 | | |
1324 | 1325 | | |
1325 | 1326 | | |
1326 | 1327 | | |
1327 | 1328 | | |
| 1329 | + | |
1328 | 1330 | | |
1329 | 1331 | | |
1330 | 1332 | | |
1331 | 1333 | | |
1332 | 1334 | | |
| 1335 | + | |
| 1336 | + | |
| 1337 | + | |
1333 | 1338 | | |
1334 | 1339 | | |
| 1340 | + | |
| 1341 | + | |
1335 | 1342 | | |
1336 | 1343 | | |
1337 | 1344 | | |
| |||
1404 | 1411 | | |
1405 | 1412 | | |
1406 | 1413 | | |
1407 | | - | |
| 1414 | + | |
1408 | 1415 | | |
1409 | 1416 | | |
1410 | 1417 | | |
| |||
1525 | 1532 | | |
1526 | 1533 | | |
1527 | 1534 | | |
| 1535 | + | |
| 1536 | + | |
1528 | 1537 | | |
1529 | 1538 | | |
1530 | 1539 | | |
| |||
0 commit comments