aboutsummaryrefslogtreecommitdiff
path: root/scripts/bpf_doc.py
diff options
context:
space:
mode:
authorMatthieu Baerts (NGI0) <[email protected]>2024-07-27 12:01:23 +0200
committerPaolo Abeni <[email protected]>2024-07-30 10:27:29 +0200
commitb6a66e521a2032f7fcba2af5a9bcbaeaa19b7ca3 (patch)
tree244ec621cec59423108dcae43814a5ac856e3407 /scripts/bpf_doc.py
parent039564d2fd37b122ec0d268e2ee6334e7169e225 (diff)
mptcp: sched: check both directions for backup
The 'mptcp_subflow_context' structure has two items related to the backup flags: - 'backup': the subflow has been marked as backup by the other peer - 'request_bkup': the backup flag has been set by the host Before this patch, the scheduler was only looking at the 'backup' flag. That can make sense in some cases, but it looks like that's not what we wanted for the general use, because either the path-manager was setting both of them when sending an MP_PRIO, or the receiver was duplicating the 'backup' flag in the subflow request. Note that the use of these two flags in the path-manager are going to be fixed in the next commits, but this change here is needed not to modify the behaviour. Fixes: f296234c98a8 ("mptcp: Add handling of incoming MP_JOIN requests") Cc: [email protected] Reviewed-by: Mat Martineau <[email protected]> Signed-off-by: Matthieu Baerts (NGI0) <[email protected]> Signed-off-by: Paolo Abeni <[email protected]>
Diffstat (limited to 'scripts/bpf_doc.py')
0 files changed, 0 insertions, 0 deletions