summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorMatthieu Baerts (NGI0) <matttbe@kernel.org>2026-05-08 18:40:46 +0300
committerJakub Kicinski <kuba@kernel.org>2026-05-12 04:01:36 +0300
commit9031e5e31d5de2c7b147a01b0a744606375ff56e (patch)
tree27f6c9ae7450c46eed40104cb0cab6b51ba41164 /include/linux
parentcb880b02117de1040b0e23a79d9c05d9a6c475b7 (diff)
downloadlinux-9031e5e31d5de2c7b147a01b0a744606375ff56e.tar.xz
mptcp: pm: in-kernel: explicitly limit batches to array size
The in-kernel PM can create subflows in reply to ADD_ADDR by batch of maximum 8 subflows for the moment. Same when adding new "subflow" endpoints with the fullmesh flag. This limit is linked to the arrays used during these steps. There was no explicit limit to the arrays size (8), because the limit of extra subflows is the same (8). It seems safer to use an explicit limit, but also these two sizes are going to be different in the next commit. Reviewed-by: Mat Martineau <martineau@kernel.org> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org> Link: https://patch.msgid.link/20260508-net-next-mptcp-pm-inc-limits-v1-1-c84e3fdf9b6a@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions