Here are various unrelated fixes:

- Patch 1: when removing an MPTCP in-kernel PM endpoint, always mark the
  corresponding ID as "available". Syzbot found a corner case where it
  is not marked as such. A fix for up to v5.10.

- Patch 2: Linked to the previous patch, the variable name was confusing
  and was probably partly responsible for the issue fixed by patch 1. No
  "Fixes" tag: no need to backport that for the moment, but better to
  avoid confusion now.

- Patch 3: fix all existing kdoc warnings linked to MPTCP code. No
  "Fixes" tag: they were there for a while, and not considered as
  important to backport.

- Patch 4: silence a compiler (false-positive) warning in the selftests.
  No "Fixes" tag: it is a false-positive warning, only seen with some
  versions.

Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
---
Matthieu Baerts (NGI0) (4):
      mptcp: pm: in-kernel: always set ID as avail when rm endp
      mptcp: pm: in-kernel: clarify mptcp_pm_remove_anno_addr()
      mptcp: fix kdoc warnings
      selftests: mptcp: connect: fix maybe-uninitialize warn

 include/uapi/linux/mptcp_pm.h                     |  2 +-
 net/mptcp/pm_kernel.c                             | 29 ++++++++++-------------
 net/mptcp/token.c                                 | 16 +++++++------
 tools/testing/selftests/net/mptcp/mptcp_connect.c |  2 +-
 4 files changed, 23 insertions(+), 26 deletions(-)
---
base-commit: 7576bd9017e35379db1ab1ef6b0e1d570eb28429
change-id: 20260204-net-mptcp-misc-fixes-6-19-rc8-6a66c86a12f7

Best regards,
-- 
Matthieu Baerts (NGI0) <[email protected]>


Reply via email to