* [PATCH mptcp-next v9 1/6] selftests: mptcp: connect: retry write() on EAGAIN
2026-10-25 13:49 [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
@ 2026-10-25 13:49 ` Anil Kaushik
2026-10-25 13:49 ` [PATCH mptcp-next v9 2/6] netlink: specs: mptcp: add the subflow-retries attribute Anil Kaushik
` (5 subsequent siblings)
6 siblings, 0 replies; 12+ messages in thread
From: Anil Kaushik @ 2026-10-25 13:49 UTC (permalink / raw)
To: mptcp; +Cc: Anil Kaushik
mptcp_connect treats any write() error as fatal. But write() can fail
with EAGAIN even after poll() said the socket was writable: the MPTCP
send buffer shrinks when a subflow is closed.
The tool then exits and the transfer fails on both sides. Instead, go
back to poll() and wait for more space. If a poll timeout is set, still
fail after as many retries, 1ms apart: poll() does not check every
cause of EAGAIN.
Fixes: 048d19d444be ("mptcp: add basic kselftest for mptcp")
Assisted-by: LLM
Signed-off-by: Anil Kaushik <anilkaushikwireless@gmail.com>
---
Notes:
v6:
- the comment says the limit only applies with a poll timeout (netdev
Sashiko)
v5:
- no change
v4:
- count the EAGAIN retries, not ms (Sashiko)
- no limit when there is no poll timeout, -t 0 (Sashiko)
v3:
- do not wait forever on EAGAIN (Sashiko)
- wrap lines over 80 columns
v2:
- Fixes tag
.../selftests/net/mptcp/mptcp_connect.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/tools/testing/selftests/net/mptcp/mptcp_connect.c b/tools/testing/selftests/net/mptcp/mptcp_connect.c
index 178d98d91fea..49017d00ab69 100644
--- a/tools/testing/selftests/net/mptcp/mptcp_connect.c
+++ b/tools/testing/selftests/net/mptcp/mptcp_connect.c
@@ -638,6 +638,7 @@ static int copyfd_io_poll(int infd, int peerfd, int outfd,
.events = POLLIN | POLLOUT,
};
unsigned int total_wlen = 0, total_rlen = 0;
+ int eagain_cnt = 0;
set_nonblock(peerfd, true);
@@ -711,6 +712,22 @@ static int copyfd_io_poll(int infd, int peerfd, int outfd,
bw = do_rnd_write(peerfd, winfo->buf + winfo->off, winfo->len);
if (bw < 0) {
+ /* POLLOUT does not guarantee that
+ * the next write will not block:
+ * the MPTCP send buffer can shrink
+ * in between, e.g. when a subflow
+ * is closed. Wait for more space,
+ * but not forever if a poll timeout
+ * is set: poll() does not check
+ * every cause of EAGAIN.
+ */
+ if (errno == EAGAIN &&
+ (poll_timeout < 0 ||
+ ++eagain_cnt <= poll_timeout)) {
+ usleep(1000);
+ continue;
+ }
+
/* expected reset, continue to read */
if (cfg_rcv_trunc &&
(errno == ECONNRESET ||
@@ -723,6 +740,7 @@ static int copyfd_io_poll(int infd, int peerfd, int outfd,
return 111;
}
+ eagain_cnt = 0;
winfo->off += bw;
winfo->len -= bw;
total_wlen += bw;
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH mptcp-next v9 2/6] netlink: specs: mptcp: add the subflow-retries attribute
2026-10-25 13:49 [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
2026-10-25 13:49 ` [PATCH mptcp-next v9 1/6] selftests: mptcp: connect: retry write() on EAGAIN Anil Kaushik
@ 2026-10-25 13:49 ` Anil Kaushik
2026-10-27 3:28 ` netdev-bot+sashiko
2026-10-25 13:49 ` [PATCH mptcp-next v9 3/6] mptcp: pm: in-kernel: add the subflow-retries limit Anil Kaushik
` (4 subsequent siblings)
6 siblings, 1 reply; 12+ messages in thread
From: Anil Kaushik @ 2026-10-25 13:49 UTC (permalink / raw)
To: mptcp; +Cc: Anil Kaushik
It will be used by the in-kernel PM to set the number of SYN
retransmissions of a subflow re-created after a timeout, with the other
limits: add it to the set-limits and get-limits commands.
The uapi header and the generated files are updated with ynl-regen.
Assisted-by: LLM
Signed-off-by: Anil Kaushik <anilkaushikwireless@gmail.com>
---
Notes:
v9:
- after a timeout, not any error, and about 4 hours with the default
RTO settings
v8:
- the default is the maximum, MAX_TCP_SYNCNT (127) (Matthieu)
v7:
- the doc gives the default value (netdev Sashiko)
v6 (netdev Sashiko):
- the policy checks the maximum value, 127 (MAX_TCP_SYNCNT)
- the doc says the value works like TCP_SYNCNT
v5:
- new, split from the retry patch (Matthieu)
Documentation/netlink/specs/mptcp_pm.yaml | 13 +++++++++++++
include/uapi/linux/mptcp_pm.h | 1 +
net/mptcp/mptcp_pm_gen.c | 10 ++++++----
net/mptcp/mptcp_pm_gen.h | 4 ++--
4 files changed, 22 insertions(+), 6 deletions(-)
diff --git a/Documentation/netlink/specs/mptcp_pm.yaml b/Documentation/netlink/specs/mptcp_pm.yaml
index 39f3facc38e5..690d3c5dfdd2 100644
--- a/Documentation/netlink/specs/mptcp_pm.yaml
+++ b/Documentation/netlink/specs/mptcp_pm.yaml
@@ -196,6 +196,16 @@ attribute-sets:
name: addr-remote
type: nest
nested-attributes: address
+ -
+ name: subflow-retries
+ type: u32
+ checks:
+ max: 127
+ doc: |
+ SYN retries of a subflow re-created after a timeout, like the
+ TCP_SYNCNT socket option, so with tcp_syn_linear_timeouts on top.
+ The default is the maximum, MAX_TCP_SYNCNT (127), about 4 hours
+ with the default RTO settings. 0 to not re-create it.
-
name: event-attr
enum-name: mptcp-event-attr
@@ -327,6 +337,7 @@ operations:
attributes:
- rcv-add-addrs
- subflows
+ - subflow-retries
-
name: get-limits
doc: Get protocol limits
@@ -337,10 +348,12 @@ operations:
attributes:
- rcv-add-addrs
- subflows
+ - subflow-retries
reply:
attributes:
- rcv-add-addrs
- subflows
+ - subflow-retries
-
name: set-flags
doc: Change endpoint flags
diff --git a/include/uapi/linux/mptcp_pm.h b/include/uapi/linux/mptcp_pm.h
index fe9863d75350..43e9643deda9 100644
--- a/include/uapi/linux/mptcp_pm.h
+++ b/include/uapi/linux/mptcp_pm.h
@@ -102,6 +102,7 @@ enum {
MPTCP_PM_ATTR_TOKEN,
MPTCP_PM_ATTR_LOC_ID,
MPTCP_PM_ATTR_ADDR_REMOTE,
+ MPTCP_PM_ATTR_SUBFLOW_RETRIES,
__MPTCP_ATTR_AFTER_LAST
};
diff --git a/net/mptcp/mptcp_pm_gen.c b/net/mptcp/mptcp_pm_gen.c
index c180930a8e0e..e2d4af1bc1d5 100644
--- a/net/mptcp/mptcp_pm_gen.c
+++ b/net/mptcp/mptcp_pm_gen.c
@@ -44,15 +44,17 @@ const struct nla_policy mptcp_pm_flush_addrs_nl_policy[MPTCP_PM_ENDPOINT_ADDR +
};
/* MPTCP_PM_CMD_SET_LIMITS - do */
-const struct nla_policy mptcp_pm_set_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOWS + 1] = {
+const struct nla_policy mptcp_pm_set_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOW_RETRIES + 1] = {
[MPTCP_PM_ATTR_RCV_ADD_ADDRS] = { .type = NLA_U32, },
[MPTCP_PM_ATTR_SUBFLOWS] = { .type = NLA_U32, },
+ [MPTCP_PM_ATTR_SUBFLOW_RETRIES] = NLA_POLICY_MAX(NLA_U32, 127),
};
/* MPTCP_PM_CMD_GET_LIMITS - do */
-const struct nla_policy mptcp_pm_get_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOWS + 1] = {
+const struct nla_policy mptcp_pm_get_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOW_RETRIES + 1] = {
[MPTCP_PM_ATTR_RCV_ADD_ADDRS] = { .type = NLA_U32, },
[MPTCP_PM_ATTR_SUBFLOWS] = { .type = NLA_U32, },
+ [MPTCP_PM_ATTR_SUBFLOW_RETRIES] = NLA_POLICY_MAX(NLA_U32, 127),
};
/* MPTCP_PM_CMD_SET_FLAGS - do */
@@ -127,7 +129,7 @@ const struct genl_ops mptcp_pm_nl_ops[11] = {
.validate = GENL_DONT_VALIDATE_STRICT,
.doit = mptcp_pm_nl_set_limits_doit,
.policy = mptcp_pm_set_limits_nl_policy,
- .maxattr = MPTCP_PM_ATTR_SUBFLOWS,
+ .maxattr = MPTCP_PM_ATTR_SUBFLOW_RETRIES,
.flags = GENL_UNS_ADMIN_PERM,
},
{
@@ -135,7 +137,7 @@ const struct genl_ops mptcp_pm_nl_ops[11] = {
.validate = GENL_DONT_VALIDATE_STRICT,
.doit = mptcp_pm_nl_get_limits_doit,
.policy = mptcp_pm_get_limits_nl_policy,
- .maxattr = MPTCP_PM_ATTR_SUBFLOWS,
+ .maxattr = MPTCP_PM_ATTR_SUBFLOW_RETRIES,
},
{
.cmd = MPTCP_PM_CMD_SET_FLAGS,
diff --git a/net/mptcp/mptcp_pm_gen.h b/net/mptcp/mptcp_pm_gen.h
index b9280bcb43f5..5b4dee8a0a34 100644
--- a/net/mptcp/mptcp_pm_gen.h
+++ b/net/mptcp/mptcp_pm_gen.h
@@ -23,9 +23,9 @@ extern const struct nla_policy mptcp_pm_get_addr_nl_policy[MPTCP_PM_ATTR_TOKEN +
extern const struct nla_policy mptcp_pm_flush_addrs_nl_policy[MPTCP_PM_ENDPOINT_ADDR + 1];
-extern const struct nla_policy mptcp_pm_set_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOWS + 1];
+extern const struct nla_policy mptcp_pm_set_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOW_RETRIES + 1];
-extern const struct nla_policy mptcp_pm_get_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOWS + 1];
+extern const struct nla_policy mptcp_pm_get_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOW_RETRIES + 1];
extern const struct nla_policy mptcp_pm_set_flags_nl_policy[MPTCP_PM_ATTR_ADDR_REMOTE + 1];
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread* Re: [PATCH mptcp-next v9 2/6] netlink: specs: mptcp: add the subflow-retries attribute
2026-10-25 13:49 ` [PATCH mptcp-next v9 2/6] netlink: specs: mptcp: add the subflow-retries attribute Anil Kaushik
@ 2026-10-27 3:28 ` netdev-bot+sashiko
0 siblings, 0 replies; 12+ messages in thread
From: netdev-bot+sashiko @ 2026-10-27 3:28 UTC (permalink / raw)
To: anilkaushikwireless; +Cc: mptcp, kuba
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] At this commit, MPTCP_PM_ATTR_SUBFLOW_RETRIES has been added to
include/uapi/linux/mptcp_pm.h and…
--
netlink: specs: mptcp: add the subflow-retries attribute
This commit adds the subflow-retries attribute to the mptcp_pm netlink
spec and the uapi header. It also adds the attribute to the set-limits
and get-limits commands, and regenerates the policies with ynl-regen.
> diff --git a/Documentation/netlink/specs/mptcp_pm.yaml b/Documentation/netlink/specs/mptcp_pm.yaml
> index 39f3facc38e55..690d3c5dfdd21 100644
> --- a/Documentation/netlink/specs/mptcp_pm.yaml
> +++ b/Documentation/netlink/specs/mptcp_pm.yaml
> @@ -196,6 +196,16 @@ attribute-sets:
> name: addr-remote
> type: nest
> nested-attributes: address
> + -
> + name: subflow-retries
> + type: u32
> + checks:
> + max: 127
> + doc: |
> + SYN retries of a subflow re-created after a timeout, like the
> + TCP_SYNCNT socket option, so with tcp_syn_linear_timeouts on top.
> + The default is the maximum, MAX_TCP_SYNCNT (127), about 4 hours
> + with the default RTO settings. 0 to not re-create it.
[ ... ]
> diff --git a/net/mptcp/mptcp_pm_gen.c b/net/mptcp/mptcp_pm_gen.c
> index c180930a8e0e4..e2d4af1bc1d5d 100644
> --- a/net/mptcp/mptcp_pm_gen.c
> +++ b/net/mptcp/mptcp_pm_gen.c
> @@ -44,15 +44,17 @@ const struct nla_policy mptcp_pm_flush_addrs_nl_policy[MPTCP_PM_ENDPOINT_ADDR +
> };
>
> /* MPTCP_PM_CMD_SET_LIMITS - do */
> -const struct nla_policy mptcp_pm_set_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOWS + 1] = {
> +const struct nla_policy mptcp_pm_set_limits_nl_policy[MPTCP_PM_ATTR_SUBFLOW_RETRIES + 1] = {
> [MPTCP_PM_ATTR_RCV_ADD_ADDRS] = { .type = NLA_U32, },
> [MPTCP_PM_ATTR_SUBFLOWS] = { .type = NLA_U32, },
> + [MPTCP_PM_ATTR_SUBFLOW_RETRIES] = NLA_POLICY_MAX(NLA_U32, 127),
> };
[Severity: Low]
After this change genl accepts and validates the attribute. At this commit,
though, mptcp_pm_nl_set_limits_doit() and mptcp_pm_nl_get_limits_doit() in
net/mptcp/pm_kernel.c only handle MPTCP_PM_ATTR_RCV_ADD_ADDRS and
MPTCP_PM_ATTR_SUBFLOWS.
Does that mean set-limits takes a subflow-retries value from 0 to 127,
returns success and then discards it? It also looks like the get-limits
reply leaves the attribute out, although the spec lists it as a reply
attribute.
The documented default (127) and the "0 to not re-create it" behaviour also
don't exist yet at this point in the series.
Because .maxattr is raised to MPTCP_PM_ATTR_SUBFLOW_RETRIES, a set-limits
or get-limits request with subflow-retries above 127 now fails with -ERANGE.
Before this change, attribute type 7 was above maxattr and was ignored
under GENL_DONT_VALIDATE_STRICT. Is that change intended at this commit?
Later in the series, "mptcp: pm: in-kernel: add the subflow-retries limit"
adds the missing pieces. mptcp_pm_nl_set_limits_doit() parses the
attribute:
attr = info->attrs[MPTCP_PM_ATTR_SUBFLOW_RETRIES];
retries = nla_get_u32_default(attr, pernet->limit_subflow_retries);
mptcp_pm_nl_get_limits_doit() emits it, and pm_nl_init_net() sets the
default to MAX_TCP_SYNCNT. Then "mptcp: pm: in-kernel: retry subflows
closed after an error" uses the value and treats 0 as "do not re-create".
So the gap is only visible when bisecting.
The commit message says the attribute "will be used by the in-kernel PM",
so the split seems deliberate. Would it be worth folding the uapi and spec
change into the implementation patch, so that no single commit exposes
the attribute without handling it?
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261025134909.2794368-1-anilkaushikwireless%40gmail.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH mptcp-next v9 3/6] mptcp: pm: in-kernel: add the subflow-retries limit
2026-10-25 13:49 [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
2026-10-25 13:49 ` [PATCH mptcp-next v9 1/6] selftests: mptcp: connect: retry write() on EAGAIN Anil Kaushik
2026-10-25 13:49 ` [PATCH mptcp-next v9 2/6] netlink: specs: mptcp: add the subflow-retries attribute Anil Kaushik
@ 2026-10-25 13:49 ` Anil Kaushik
2026-10-25 13:49 ` [PATCH mptcp-next v9 4/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
` (3 subsequent siblings)
6 siblings, 0 replies; 12+ messages in thread
From: Anil Kaushik @ 2026-10-25 13:49 UTC (permalink / raw)
To: mptcp; +Cc: Anil Kaushik
A new limit for the in-kernel PM, set and read with the other limits:
the number of SYN retries of a subflow re-created after a timeout, like
the TCP_SYNCNT socket option. The default is the maximum, MAX_TCP_SYNCNT
(127), about 4 hours, and 0 to not re-create it. The netlink policy
checks this maximum value.
It is also exposed in struct mptcp_info, in place of the reserved field.
The next patch uses it.
Assisted-by: LLM
Signed-off-by: Anil Kaushik <anilkaushikwireless@gmail.com>
---
Notes:
v9:
- MAX_TCP_SYNCNT instead of 127 for the default
- after a timeout, not any error
v8:
- the default is the maximum, 127, about 4 hours (Matthieu)
v6:
- the netlink policy checks the maximum, no more parse_limit() change
(netdev Sashiko)
- the limit works like TCP_SYNCNT, say so (netdev Sashiko)
v5:
- new, split from the retry patch (Matthieu)
- the limit is also in struct mptcp_info (Matthieu)
include/uapi/linux/mptcp.h | 2 +-
net/mptcp/pm_kernel.c | 23 ++++++++++++++++++++++-
net/mptcp/protocol.h | 1 +
net/mptcp/sockopt.c | 2 ++
4 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/mptcp.h b/include/uapi/linux/mptcp.h
index 72a5d030154e..d7e3f359773d 100644
--- a/include/uapi/linux/mptcp.h
+++ b/include/uapi/linux/mptcp.h
@@ -72,7 +72,7 @@ struct mptcp_info {
__u8 mptcpi_subflows_total;
__u8 mptcpi_endp_laminar_max;
__u8 mptcpi_endp_fullmesh_max;
- __u8 reserved;
+ __u8 mptcpi_limit_subflow_retries;
__u32 mptcpi_last_data_sent;
__u32 mptcpi_last_data_recv;
__u32 mptcpi_last_ack_recv;
diff --git a/net/mptcp/pm_kernel.c b/net/mptcp/pm_kernel.c
index d3014bf57bf3..7fb4c7874340 100644
--- a/net/mptcp/pm_kernel.c
+++ b/net/mptcp/pm_kernel.c
@@ -25,6 +25,7 @@ struct pm_nl_pernet {
u8 endp_fullmesh_max;
u8 limit_add_addr_accepted;
u8 limit_extra_subflows;
+ u8 limit_subflow_retries;
u8 next_id;
DECLARE_BITMAP(id_bitmap, MPTCP_PM_MAX_ADDR_ID + 1);
};
@@ -96,6 +97,14 @@ u8 mptcp_pm_get_limit_extra_subflows(const struct mptcp_sock *msk)
}
EXPORT_SYMBOL_GPL(mptcp_pm_get_limit_extra_subflows);
+u8 mptcp_pm_get_limit_subflow_retries(const struct mptcp_sock *msk)
+{
+ struct pm_nl_pernet *pernet = pm_nl_get_pernet_from_msk(msk);
+
+ return READ_ONCE(pernet->limit_subflow_retries);
+}
+EXPORT_SYMBOL_GPL(mptcp_pm_get_limit_subflow_retries);
+
static bool has_subflow_daddr(const struct mptcp_sock *msk,
const struct mptcp_addr_info *daddr)
{
@@ -1419,7 +1428,8 @@ static int parse_limit(struct genl_info *info, int id, unsigned int *limit)
int mptcp_pm_nl_set_limits_doit(struct sk_buff *skb, struct genl_info *info)
{
struct pm_nl_pernet *pernet = genl_info_pm_nl(info);
- unsigned int rcv_addrs, subflows;
+ unsigned int rcv_addrs, subflows, retries;
+ struct nlattr *attr;
int ret;
spin_lock_bh(&pernet->lock);
@@ -1433,8 +1443,13 @@ int mptcp_pm_nl_set_limits_doit(struct sk_buff *skb, struct genl_info *info)
if (ret)
goto unlock;
+ /* the maximum, MAX_TCP_SYNCNT, is checked by the policy */
+ attr = info->attrs[MPTCP_PM_ATTR_SUBFLOW_RETRIES];
+ retries = nla_get_u32_default(attr, pernet->limit_subflow_retries);
+
WRITE_ONCE(pernet->limit_add_addr_accepted, rcv_addrs);
WRITE_ONCE(pernet->limit_extra_subflows, subflows);
+ WRITE_ONCE(pernet->limit_subflow_retries, retries);
unlock:
spin_unlock_bh(&pernet->lock);
@@ -1464,6 +1479,10 @@ int mptcp_pm_nl_get_limits_doit(struct sk_buff *skb, struct genl_info *info)
READ_ONCE(pernet->limit_extra_subflows)))
goto fail;
+ if (nla_put_u32(msg, MPTCP_PM_ATTR_SUBFLOW_RETRIES,
+ READ_ONCE(pernet->limit_subflow_retries)))
+ goto fail;
+
genlmsg_end(msg, reply);
return genlmsg_reply(msg, info);
@@ -1618,6 +1637,8 @@ static int __net_init pm_nl_init_net(struct net *net)
/* Cit. 2 subflows ought to be enough for anybody. */
pernet->limit_extra_subflows = 2;
+ /* the maximum: about 4 hours with the default RTOs */
+ pernet->limit_subflow_retries = MAX_TCP_SYNCNT;
pernet->next_id = 1;
spin_lock_init(&pernet->lock);
diff --git a/net/mptcp/protocol.h b/net/mptcp/protocol.h
index 3be60da12924..4aa4aedb2ba7 100644
--- a/net/mptcp/protocol.h
+++ b/net/mptcp/protocol.h
@@ -1266,6 +1266,7 @@ u8 mptcp_pm_get_endp_laminar_max(const struct mptcp_sock *msk);
u8 mptcp_pm_get_endp_fullmesh_max(const struct mptcp_sock *msk);
u8 mptcp_pm_get_limit_add_addr_accepted(const struct mptcp_sock *msk);
u8 mptcp_pm_get_limit_extra_subflows(const struct mptcp_sock *msk);
+u8 mptcp_pm_get_limit_subflow_retries(const struct mptcp_sock *msk);
/* called under PM lock */
static inline void __mptcp_pm_close_subflow(struct mptcp_sock *msk)
diff --git a/net/mptcp/sockopt.c b/net/mptcp/sockopt.c
index 922f6ae5c80c..d3c4abf59ec5 100644
--- a/net/mptcp/sockopt.c
+++ b/net/mptcp/sockopt.c
@@ -1075,6 +1075,8 @@ void mptcp_diag_fill_info(struct mptcp_sock *msk, struct mptcp_info *info)
mptcp_pm_get_endp_laminar_max(msk);
info->mptcpi_endp_fullmesh_max =
mptcp_pm_get_endp_fullmesh_max(msk);
+ info->mptcpi_limit_subflow_retries =
+ mptcp_pm_get_limit_subflow_retries(msk);
}
if (__mptcp_check_fallback(msk))
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH mptcp-next v9 4/6] mptcp: pm: in-kernel: retry subflows closed after an error
2026-10-25 13:49 [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
` (2 preceding siblings ...)
2026-10-25 13:49 ` [PATCH mptcp-next v9 3/6] mptcp: pm: in-kernel: add the subflow-retries limit Anil Kaushik
@ 2026-10-25 13:49 ` Anil Kaushik
2026-10-25 14:21 ` sashiko-bot
2026-10-27 3:28 ` netdev-bot+sashiko
2026-10-25 13:49 ` [PATCH mptcp-next v9 5/6] selftests: mptcp: pm_nl_ctl: support the subflow-retries limit Anil Kaushik
` (2 subsequent siblings)
6 siblings, 2 replies; 12+ messages in thread
From: Anil Kaushik @ 2026-10-25 13:49 UTC (permalink / raw)
To: mptcp; +Cc: Anil Kaushik
With the in-kernel PM, a subflow closed after an error, e.g. a timeout
when a path silently drops packets, is never re-created, even once the
path works again. For example, with a main link and a backup link,
connections move to the backup after an outage but never come back.
When TCP gives up on an established subflow created by this side, after
a retransmission or keepalive timeout, whatever ICMP error was received
from the path before, the PM now creates a new one with the same
addresses. Its SYN retries, set like TCP_SYNCNT by the subflow-retries
limit, space out the attempts. This is a single connection attempt: an
ICMP error, or a local error when connecting, ends it, and it is not
retried again. It is also closed if the MPTCP socket is closed in the
meantime. If no other subflow can send data, the connection is still
closed after the close timeout, as when all the subflows are closed,
unless the new subflow connects before. Once it is established, it is
handled like any other subflow. Re-creating the initial subflow uses one
of the additional subflows allowed by the limits.
__mptcp_close_ssk() now always cleans the references to the closed
subflow in the MPTCP backlog, not only with MPTCP_CF_PUSH: a re-created
subflow closed with the MPTCP socket can get established in between.
The other paths without MPTCP_CF_PUSH have already purged the backlog.
A subflow reset by the peer, or by anything on the path, is not
re-created: the path works, and re-creating it right away could loop.
A subflow that never got established is not re-created either: the PM
keeps trying the next endpoints, as before. Subflows aborted locally,
also by MPTCP, or using an address that has been removed are not
retried.
TCP only closes a subflow after tcp_retries2 retransmissions, about 15
minutes by default. A subflow that only receives data never gets an
error: the application has to enable TCP keepalive on the MPTCP socket,
which MPTCP applies to all the subflows. Both are documented in
mptcp.rst.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/440
Assisted-by: LLM
Signed-off-by: Anil Kaushik <anilkaushikwireless@gmail.com>
---
Notes:
v9:
- every timeout is retried, whatever ICMP error TCP reports for it,
the last one received, see tcp_write_err(): resets, local aborts
and MPTCP protocol errors are excluded instead of listing the
timeout errors, so IPv4 and IPv6 behave the same (netdev Sashiko)
- mptcp.rst: 0 does not re-create the subflows (netdev Sashiko)
- the re-created subflows closed with the msk get no SUB_CLOSED
event, like the other subflows closed with it
- if no other subflow can send data, the close timeout still applies:
creating the new subflow no longer keeps the connection open for
the whole SYN retries
- doc and commit message: a single connection attempt, ended by an
ICMP error or a local connect error
- __mptcp_close_ssk() always cleans the msk backlog of the closed
subflow: a re-created subflow closed with the msk can have been
established in between, with data in the backlog (netdev Sashiko).
It is still closed without MPTCP_CF_PUSH, which would re-send all
the pending data
- tcp_sock_set_syncnt(), without the ssk lock
v8:
- mptcp.rst gives the default, 127, about 4 hours
- close the re-created subflows still connecting before
__mptcp_wr_shutdown() disconnects them, and also the already
disconnected ones, e.g. after shutdown(SHUT_WR) (sashiko.dev)
- mptcp.rst: the initial subflow on the client side, the subflows
limit, and only one attempt (netdev Sashiko)
v7:
- only after a path error, a retransmission or keepalive timeout: a
reset from the peer or the path could make it loop (netdev
Sashiko)
- retry and no_retry are bools under the msk socket lock, in the
padding after close_event_done, not bits next to the reset ones
(netdev Sashiko)
- mark all the subflows using a removed address, whatever their
state (netdev Sashiko)
- doc: tcp_retries2, and keepalive for a subflow that only receives
data (Abdul Wasey's tests)
- not retried after a reset by MPTCP itself, even with an old sk_err
left by IP_RECVERR (netdev Sashiko)
- close the re-created subflows still connecting without
MPTCP_CF_PUSH: they never carried data (netdev Sashiko)
v6 (netdev Sashiko):
- only re-create subflows that were established: the PM still tries the
next endpoints when one never gets established
- only once TCP closed the subflow, to read its reset flags safely
- removed addresses, also the remote ones and the local ID 0: the dead
subflows are marked in mptcp_pm_rm_addr_or_subflow(), instead of
looking up the endpoint
v5 (Matthieu):
- split in 4 patches
- reverse xmas tree in mptcp_pm_kernel_retry_check()
- "in-kernel" in the subject, like the other in-kernel PM patches
- close the re-created subflows still connecting when the socket is
closed (Matthieu: closing the socket during a retry)
v4 (Matthieu):
- netlink limit, on by default, instead of the sysctl
- one new subflow per failure, its SYN retries set from the limit: no
socket reuse, no attempts counter, no 60s check
- no MIB counter
- not retried if the endpoint was removed, instead of the pm.c change
- called through pm.c
- new bit in the subflow context, no new hole
- commit message: MP_RST, not any RST (Sashiko)
v3 (Sashiko):
- no retry after MP_RST without the T flag, local abort or EBADMSG
- no retry on a removed endpoint or address
- use only request_bkup for the backup flag
v2:
- use the subflow sockets, no list or timer
- code moved to pm_kernel.c
Documentation/networking/mptcp.rst | 18 +++++
net/mptcp/pm.c | 39 ++++++++++
net/mptcp/pm_kernel.c | 118 +++++++++++++++++++++++++++++
net/mptcp/protocol.c | 77 ++++++++++++++++++-
net/mptcp/protocol.h | 19 +++++
5 files changed, 269 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/mptcp.rst b/Documentation/networking/mptcp.rst
index b6753ffb9c9a..8a2c9b9d2a4f 100644
--- a/Documentation/networking/mptcp.rst
+++ b/Documentation/networking/mptcp.rst
@@ -73,6 +73,24 @@ To be able to use multiple IP addresses on a host to create multiple *subflows*
addresses can be used. This can be configured with ``ip mptcp endpoint`` for
example.
+When TCP gives up on an established subflow created by this host, after a
+retransmission or keepalive timeout, the in-kernel path manager creates it
+again, with the ``subflow-retries`` limit as its number of SYN retries, like
+``TCP_SYNCNT``: 127 by default, about 4 hours, and 0 to not re-create it. This
+is done for the additional subflows, and for the initial one on the client side:
+the new subflow then takes one of the additional subflows allowed by the
+``subflows`` limit. This is a single connection attempt: an ICMP error, or a
+local error when connecting, ends it, and it is not created again. If no other
+subflow can send data in the meantime, the connection is closed after
+``close_timeout``, as when all the subflows are closed, unless the new subflow
+connects before. A subflow reset by the peer, or by anything on the path, is not
+created again either. TCP only gives up on a subflow after ``tcp_retries2``
+retransmissions, about 15 minutes by default: shorter outages are handled by TCP
+itself. A subflow that only receives data does not notice that its path stopped
+working: the application should then enable TCP keepalive on the MPTCP socket
+(``SO_KEEPALIVE``, ``TCP_KEEPIDLE``, ``TCP_KEEPINTVL`` and ``TCP_KEEPCNT``),
+which MPTCP applies to all its subflows.
+
Packet Scheduler
----------------
diff --git a/net/mptcp/pm.c b/net/mptcp/pm.c
index d7c5b50b34cc..2bb08be95cd1 100644
--- a/net/mptcp/pm.c
+++ b/net/mptcp/pm.c
@@ -694,6 +694,26 @@ void mptcp_pm_subflow_check_next(struct mptcp_sock *msk,
spin_unlock_bh(&pm->lock);
}
+/* Called with the msk socket lock held, before closing a subflow: true if
+ * it has to be re-created once closed, see mptcp_pm_subflow_retry().
+ */
+bool mptcp_pm_subflow_retry_check(struct mptcp_sock *msk,
+ const struct mptcp_subflow_context *subflow,
+ struct mptcp_pm_retry *retry)
+{
+ if (!mptcp_pm_is_kernel(msk))
+ return false;
+
+ return mptcp_pm_kernel_retry_check(msk, subflow, retry);
+}
+
+void mptcp_pm_subflow_retry(struct mptcp_sock *msk,
+ const struct mptcp_pm_retry *retry)
+{
+ if (mptcp_pm_is_kernel(msk))
+ mptcp_pm_kernel_retry(msk, retry);
+}
+
void mptcp_pm_add_addr_received(const struct sock *ssk,
const struct mptcp_addr_info *addr)
{
@@ -762,6 +782,24 @@ static void mptcp_pm_add_addr_send_ack(struct mptcp_sock *msk)
mptcp_pm_schedule_work(msk, MPTCP_PM_ADD_ADDR_SEND_ACK);
}
+/* A subflow using a removed address must not be re-created, whatever its
+ * state, e.g. closed by TCP but not collected yet, see
+ * mptcp_pm_kernel_retry_check().
+ */
+static void mptcp_pm_rm_no_retry(struct mptcp_subflow_context *subflow,
+ enum linux_mptcp_mib_field rm_type, u8 rm_id)
+{
+ u8 id;
+
+ if (rm_type == MPTCP_MIB_RMADDR)
+ id = READ_ONCE(subflow->remote_id);
+ else
+ id = subflow_get_local_id(subflow);
+
+ if (id == rm_id)
+ subflow->no_retry = true;
+}
+
static void mptcp_pm_rm_addr_or_subflow(struct mptcp_sock *msk,
const struct mptcp_rm_list *rm_list,
enum linux_mptcp_mib_field rm_type)
@@ -794,6 +832,7 @@ static void mptcp_pm_rm_addr_or_subflow(struct mptcp_sock *msk,
int how = RCV_SHUTDOWN | SEND_SHUTDOWN;
u8 id = subflow_get_local_id(subflow);
+ mptcp_pm_rm_no_retry(subflow, rm_type, rm_id);
if ((1 << inet_sk_state_load(ssk)) &
(TCPF_FIN_WAIT1 | TCPF_FIN_WAIT2 | TCPF_CLOSING | TCPF_CLOSE))
continue;
diff --git a/net/mptcp/pm_kernel.c b/net/mptcp/pm_kernel.c
index 7fb4c7874340..de84aecd6a62 100644
--- a/net/mptcp/pm_kernel.c
+++ b/net/mptcp/pm_kernel.c
@@ -1610,6 +1610,124 @@ bool mptcp_pm_nl_check_work_pending(struct mptcp_sock *msk)
return true;
}
+/* TCP gave up on the path: after a retransmission, keepalive or user
+ * timeout, sk_err is ETIMEDOUT, or the last ICMP error received from the
+ * path, see tcp_write_err(). The other errors on an established subflow
+ * are not path failures: a reset, from the peer or from anything on the
+ * path (ECONNRESET, or EPIPE in CLOSE_WAIT, see tcp_reset()), a local
+ * abort (ECONNABORTED), or an MPTCP protocol error (EBADMSG).
+ */
+static bool mptcp_pm_retry_path_error(int err)
+{
+ switch (err) {
+ case ECONNRESET:
+ case EPIPE:
+ case ECONNABORTED:
+ case EBADMSG:
+ return false;
+ }
+
+ return true;
+}
+
+/* Called with the msk socket lock held, before the subflow is closed */
+bool mptcp_pm_kernel_retry_check(struct mptcp_sock *msk,
+ const struct mptcp_subflow_context *subflow,
+ struct mptcp_pm_retry *retry)
+{
+ struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
+ struct sock *sk = (struct sock *)msk;
+ int err;
+
+ /* Only once TCP closed it: the acquire in inet_sk_state_load() makes
+ * sure sk_err and the resetting flag checked below are the ones of
+ * this close.
+ */
+ if (inet_sk_state_load(ssk) != TCP_CLOSE)
+ return false;
+
+ err = READ_ONCE(ssk->sk_err);
+ retry->syn_retries = mptcp_pm_get_limit_subflow_retries(msk);
+ if (!retry->syn_retries || !err || sk->sk_state != TCP_ESTABLISHED ||
+ __mptcp_check_fallback(msk))
+ return false;
+
+ /* mptcp_close_ssk() will not handle it again, e.g. the initial
+ * subflow, kept in the list once closed
+ */
+ if (subflow->close_event_done || READ_ONCE(subflow->local_id) < 0)
+ return false;
+
+ /* Only a path that worked is tried again. If a subflow never got
+ * established, the PM moves on to the next endpoints instead, and a
+ * re-created subflow that cannot connect is not retried again: its SYN
+ * retransmissions already spaced out the tries.
+ */
+ if (!READ_ONCE(subflow->fully_established))
+ return false;
+
+ /* its address has been removed, see mptcp_pm_rm_addr_or_subflow() */
+ if (subflow->no_retry)
+ return false;
+
+ /* Only when the path stopped working. A reset, from the peer or from
+ * anything on the path, means the path works: re-creating the subflow
+ * right away could loop. Not after a reset by MPTCP itself either, with
+ * mptcp_subflow_reset(), whatever sk_err says.
+ */
+ if (!mptcp_pm_retry_path_error(err) || subflow->resetting)
+ return false;
+
+ /* Only re-create subflows initiated by this side: MP_JOIN ones, or the
+ * initial one on the client side.
+ */
+ if (!subflow->request_join &&
+ (subflow->mp_join || READ_ONCE(msk->pm.server_side)))
+ return false;
+
+ mptcp_remote_address((struct sock_common *)ssk, &retry->remote);
+ retry->remote.id = READ_ONCE(subflow->remote_id);
+ if (!retry->remote.id && READ_ONCE(msk->pm.remote_deny_join_id0))
+ return false;
+
+ mptcp_local_address((struct sock_common *)ssk, &retry->local.addr);
+ retry->local.addr.port = 0;
+ retry->local.addr.id = subflow_get_local_id(subflow);
+ retry->local.flags = subflow->request_bkup ?
+ MPTCP_PM_ADDR_FLAG_BACKUP : 0;
+ retry->local.ifindex = ssk->sk_bound_dev_if;
+
+ return true;
+}
+
+/* Called with the msk socket lock held, after the subflow has been closed */
+void mptcp_pm_kernel_retry(struct mptcp_sock *msk,
+ const struct mptcp_pm_retry *retry)
+{
+ struct mptcp_subflow_context *subflow;
+ struct sock *sk = (struct sock *)msk;
+ bool allowed;
+
+ spin_lock_bh(&msk->pm.lock);
+ allowed = msk->pm.extra_subflows <
+ mptcp_pm_get_limit_extra_subflows(msk);
+ if (allowed)
+ msk->pm.extra_subflows++;
+ spin_unlock_bh(&msk->pm.lock);
+
+ if (!allowed ||
+ __mptcp_subflow_connect(sk, &retry->local, &retry->remote))
+ return;
+
+ /* the new subflow is the last one */
+ subflow = list_last_entry(&msk->conn_list, struct mptcp_subflow_context,
+ node);
+ /* from 1 to MAX_TCP_SYNCNT, see mptcp_pm_kernel_retry_check() */
+ tcp_sock_set_syncnt(mptcp_subflow_tcp_sock(subflow),
+ retry->syn_retries);
+ subflow->retry = true;
+}
+
/* Called under PM lock */
void __mptcp_pm_kernel_worker(struct mptcp_sock *msk)
{
diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
index 02a4f479d9d8..25fd0628686c 100644
--- a/net/mptcp/protocol.c
+++ b/net/mptcp/protocol.c
@@ -2697,8 +2697,11 @@ static void __mptcp_close_ssk(struct sock *sk, struct sock *ssk,
lock_sock_nested(ssk, SINGLE_DEPTH_NESTING);
subflow->closing = 1;
- if (flags & MPTCP_CF_PUSH)
- mptcp_cleanup_ssk_backlog(sk, ssk);
+ /* also without MPTCP_CF_PUSH: a re-created subflow closed with the msk
+ * can have been established in between, see
+ * mptcp_close_retry_subflows()
+ */
+ mptcp_cleanup_ssk_backlog(sk, ssk);
/* Borrow the fwd allocated page left-over; fwd memory for the subflow
* could be negative at this point, but will be reach zero soon - when
@@ -2788,6 +2791,32 @@ static void __mptcp_close_ssk(struct sock *sk, struct sock *ssk,
}
}
+/* With no subflow left to send data, a re-created subflow still connecting
+ * must not keep the connection open longer than the close timeout, as when
+ * all the subflows are closed, see __mptcp_close_ssk(). A join stops it.
+ */
+static void mptcp_retry_check_tout(struct sock *sk)
+{
+ struct mptcp_subflow_context *subflow;
+ struct mptcp_sock *msk = mptcp_sk(sk);
+ bool connecting = false;
+
+ if (sk->sk_state != TCP_ESTABLISHED ||
+ inet_csk(sk)->icsk_mtup.probe_timestamp)
+ return;
+
+ mptcp_for_each_subflow(msk, subflow) {
+ if (__mptcp_subflow_active(subflow))
+ return;
+
+ connecting |= subflow->retry &&
+ !READ_ONCE(subflow->fully_established);
+ }
+
+ if (connecting)
+ mptcp_start_tout_timer(sk);
+}
+
void mptcp_close_ssk(struct sock *sk, struct sock *ssk,
struct mptcp_subflow_context *subflow)
{
@@ -2806,6 +2835,7 @@ void mptcp_close_ssk(struct sock *sk, struct sock *ssk,
mptcp_pm_subflow_check_next(mptcp_sk(sk), subflow);
__mptcp_close_ssk(sk, ssk, subflow, MPTCP_CF_PUSH);
+ mptcp_retry_check_tout(sk);
}
static unsigned int mptcp_sync_mss(struct sock *sk, u32 pmtu)
@@ -2823,6 +2853,8 @@ static void __mptcp_close_subflow(struct sock *sk)
mptcp_for_each_subflow_safe(msk, subflow, tmp) {
struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
int ssk_state = inet_sk_state_load(ssk);
+ struct mptcp_pm_retry retry;
+ bool do_retry;
if (ssk_state != TCP_CLOSE &&
(ssk_state != TCP_CLOSE_WAIT ||
@@ -2834,7 +2866,13 @@ static void __mptcp_close_subflow(struct sock *sk)
if (!skb_queue_empty_lockless(&ssk->sk_receive_queue))
continue;
+ do_retry = mptcp_pm_subflow_retry_check(msk, subflow, &retry);
mptcp_close_ssk(sk, ssk, subflow);
+ if (do_retry) {
+ mptcp_pm_subflow_retry(msk, &retry);
+ /* creating a subflow stopped the close timeout */
+ mptcp_retry_check_tout(sk);
+ }
}
}
@@ -3501,6 +3539,38 @@ static void mptcp_check_listen_stop(struct sock *sk)
release_sock(ssk);
}
+/* Re-created subflows still connecting are useless once the msk is closed:
+ * they would keep it around until the close timeout.
+ */
+static void mptcp_close_retry_subflows(struct sock *sk)
+{
+ struct mptcp_subflow_context *subflow, *tmp;
+ struct mptcp_sock *msk = mptcp_sk(sk);
+
+ mptcp_for_each_subflow_safe(msk, subflow, tmp) {
+ struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
+ int state;
+
+ if (!subflow->retry || READ_ONCE(subflow->fully_established))
+ continue;
+
+ /* still connecting, or already disconnected by
+ * mptcp_subflow_shutdown(), e.g. after shutdown(SHUT_WR)
+ */
+ state = inet_sk_state_load(ssk);
+ if (state != TCP_SYN_SENT && state != TCP_CLOSE)
+ continue;
+
+ /* Checked without the ssk lock: it can have been established
+ * in between. __mptcp_close_ssk() cleans its data in the msk
+ * backlog, and the MPTCP retransmissions cover what it sent.
+ * No need to push the pending data again.
+ */
+ mptcp_pm_subflow_check_next(msk, subflow);
+ __mptcp_close_ssk(sk, ssk, subflow, 0);
+ }
+}
+
bool __mptcp_close(struct sock *sk, long timeout)
{
struct mptcp_subflow_context *subflow;
@@ -3516,6 +3586,9 @@ bool __mptcp_close(struct sock *sk, long timeout)
goto cleanup;
}
+ /* before __mptcp_wr_shutdown() disconnects them */
+ mptcp_close_retry_subflows(sk);
+
if (mptcp_data_avail(msk) || timeout < 0 ||
(sock_flag(sk, SOCK_LINGER) && !sk->sk_lingertime)) {
/* If the msk has read data, or the caller explicitly ask it,
diff --git a/net/mptcp/protocol.h b/net/mptcp/protocol.h
index 4aa4aedb2ba7..d47430fc7dc8 100644
--- a/net/mptcp/protocol.h
+++ b/net/mptcp/protocol.h
@@ -610,6 +610,8 @@ struct mptcp_subflow_context {
bool close_event_done; /* has done the post-closed part,
* protected by msk socket lock
*/
+ bool retry; /* re-created after an error, msk lock */
+ bool no_retry; /* uses a removed address, msk lock */
u32 lent_mem_frag;
u32 remote_nonce;
u32 local_nonce;
@@ -1139,6 +1141,18 @@ void mptcp_pm_subflow_established(struct mptcp_sock *msk);
bool mptcp_pm_nl_check_work_pending(struct mptcp_sock *msk);
void mptcp_pm_subflow_check_next(struct mptcp_sock *msk,
const struct mptcp_subflow_context *subflow);
+
+struct mptcp_pm_retry {
+ struct mptcp_pm_local local;
+ struct mptcp_addr_info remote;
+ u8 syn_retries;
+};
+
+bool mptcp_pm_subflow_retry_check(struct mptcp_sock *msk,
+ const struct mptcp_subflow_context *subflow,
+ struct mptcp_pm_retry *retry);
+void mptcp_pm_subflow_retry(struct mptcp_sock *msk,
+ const struct mptcp_pm_retry *retry);
void mptcp_pm_add_addr_received(const struct sock *ssk,
const struct mptcp_addr_info *addr);
void mptcp_pm_add_addr_echoed(struct mptcp_sock *msk,
@@ -1260,6 +1274,11 @@ void __init mptcp_pm_userspace_register(void);
void __init mptcp_pm_nl_init(void);
void mptcp_pm_worker(struct mptcp_sock *msk);
void __mptcp_pm_kernel_worker(struct mptcp_sock *msk);
+bool mptcp_pm_kernel_retry_check(struct mptcp_sock *msk,
+ const struct mptcp_subflow_context *subflow,
+ struct mptcp_pm_retry *retry);
+void mptcp_pm_kernel_retry(struct mptcp_sock *msk,
+ const struct mptcp_pm_retry *retry);
u8 mptcp_pm_get_endp_signal_max(const struct mptcp_sock *msk);
u8 mptcp_pm_get_endp_subflow_max(const struct mptcp_sock *msk);
u8 mptcp_pm_get_endp_laminar_max(const struct mptcp_sock *msk);
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread* Re: [PATCH mptcp-next v9 4/6] mptcp: pm: in-kernel: retry subflows closed after an error
2026-10-25 13:49 ` [PATCH mptcp-next v9 4/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
@ 2026-10-25 14:21 ` sashiko-bot
2026-10-27 3:28 ` netdev-bot+sashiko
1 sibling, 0 replies; 12+ messages in thread
From: sashiko-bot @ 2026-10-25 14:21 UTC (permalink / raw)
To: Anil Kaushik, mptcp
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] mptcp: close timeout from mptcp_retry_check_tout() not stopped on retry join
- [Medium] mptcp: pm: retry subflows keep half-closed sockets open when all subflows close
--
commit 92b3e7c79536b83b9f6407cb01792ce3da0243f5
Author: Anil Kaushik <anilkaushikwireless@gmail.com>
mptcp: pm: in-kernel: retry subflows closed after an error
This commit updates the in-kernel path manager to re-create established
subflows initiated by the local host when TCP closes them after a
retransmission or keepalive timeout, using the subflow-retries limit for SYN
retransmissions. It also cleans up connecting retry subflows on socket close
and starts the close timeout timer if no active subflows remain while a retry
subflow is connecting.
> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> index 02a4f479d9d8c..25fd0628686c3 100644
> --- a/net/mptcp/protocol.c
> +++ b/net/mptcp/protocol.c
[ ... ]
> @@ -2788,6 +2791,32 @@ static void __mptcp_close_ssk(struct sock *sk, struct sock *ssk,
> }
> }
>
> +/* With no subflow left to send data, a re-created subflow still connecting
> + * must not keep the connection open longer than the close timeout, as when
> + * all the subflows are closed, see __mptcp_close_ssk(). A join stops it.
> + */
> +static void mptcp_retry_check_tout(struct sock *sk)
> +{
> + struct mptcp_subflow_context *subflow;
> + struct mptcp_sock *msk = mptcp_sk(sk);
> + bool connecting = false;
> +
> + if (sk->sk_state != TCP_ESTABLISHED ||
> + inet_csk(sk)->icsk_mtup.probe_timestamp)
> + return;
[Severity: Medium]
What happens if sk transitions out of TCP_ESTABLISHED while a re-created
subflow is still connecting in TCP_SYN_SENT, and the remaining active
subflows subsequently close before close() is called?
For example, if subflow 1 times out while sk->sk_state is TCP_ESTABLISHED,
__mptcp_close_subflow() -> mptcp_pm_subflow_retry() creates a retry subflow
in TCP_SYN_SENT while subflow 2 is still active.
If the peer then sends DATA_FIN on subflow 2 (moving sk->sk_state to
TCP_CLOSE_WAIT in mptcp_check_data_fin()), or the application calls
shutdown(fd, SHUT_WR) with unsent data still queued (moving sk->sk_state to
TCP_FIN_WAIT1 in mptcp_shutdown() while mptcp_check_send_data_fin() returns
before calling mptcp_subflow_shutdown()), mptcp_close_retry_subflows() is not
called because it only runs from __mptcp_close(). At that point,
mptcp_is_fully_established(sk) is false, so mptcp_finish_join() will reject
the connecting retry subflow even if the path recovers.
If subflow 2 later closes via mptcp_close_ssk(), __mptcp_close_ssk() checks
list_is_singular(&msk->conn_list), which is false because the connecting
retry subflow is still in msk->conn_list alongside msk->first:
net/mptcp/protocol.c:__mptcp_close_ssk() {
...
if (list_is_singular(&msk->conn_list) && msk->first &&
inet_sk_state_load(msk->first) == TCP_CLOSE) {
if (sk->sk_state != TCP_ESTABLISHED ||
msk->in_accept_queue || sock_flag(sk, SOCK_DEAD)) {
mptcp_set_state(sk, TCP_CLOSE);
mptcp_close_wake_up(sk);
} else {
mptcp_start_tout_timer(sk);
}
}
}
Then mptcp_retry_check_tout() returns early because sk->sk_state is no longer
TCP_ESTABLISHED. Doesn't this leave the half-closed MPTCP socket open without
a close timeout timer until all 127 SYN retries on the retry subflow expire?
> +
> + mptcp_for_each_subflow(msk, subflow) {
> + if (__mptcp_subflow_active(subflow))
> + return;
> +
> + connecting |= subflow->retry &&
> + !READ_ONCE(subflow->fully_established);
> + }
> +
> + if (connecting)
> + mptcp_start_tout_timer(sk);
> +}
>
> void mptcp_close_ssk(struct sock *sk, struct sock *ssk,
> struct mptcp_subflow_context *subflow)
> @@ -2806,6 +2835,7 @@ void mptcp_close_ssk(struct sock *sk, struct sock *ssk,
> mptcp_pm_subflow_check_next(mptcp_sk(sk), subflow);
>
> __mptcp_close_ssk(sk, ssk, subflow, MPTCP_CF_PUSH);
> + mptcp_retry_check_tout(sk);
> }
>
> static unsigned int mptcp_sync_mss(struct sock *sk, u32 pmtu)
> @@ -2823,6 +2853,8 @@ static void __mptcp_close_subflow(struct sock *sk)
> mptcp_for_each_subflow_safe(msk, subflow, tmp) {
> struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
> int ssk_state = inet_sk_state_load(ssk);
> + struct mptcp_pm_retry retry;
> + bool do_retry;
>
> if (ssk_state != TCP_CLOSE &&
> (ssk_state != TCP_CLOSE_WAIT ||
> @@ -2834,7 +2866,13 @@ static void __mptcp_close_subflow(struct sock *sk)
> if (!skb_queue_empty_lockless(&ssk->sk_receive_queue))
> continue;
>
> + do_retry = mptcp_pm_subflow_retry_check(msk, subflow, &retry);
> mptcp_close_ssk(sk, ssk, subflow);
> + if (do_retry) {
> + mptcp_pm_subflow_retry(msk, &retry);
> + /* creating a subflow stopped the close timeout */
> + mptcp_retry_check_tout(sk);
> + }
[Severity: High]
Where is the close timeout timer stopped once the re-created subflow finishes
connecting and joins the connection?
When the last active subflow closes and is retried here in
__mptcp_close_subflow(), mptcp_pm_subflow_retry() -> mptcp_pm_kernel_retry()
calls __mptcp_subflow_connect(), which adds subflow->node to msk->conn_list,
starts the non-blocking connect, and calls mptcp_stop_tout_timer(sk).
Immediately after mptcp_pm_subflow_retry() returns (or in mptcp_close_ssk()
when another last active subflow closes while a retry subflow is connecting),
mptcp_retry_check_tout(sk) sees no active subflows and calls
mptcp_start_tout_timer(sk), setting inet_csk(sk)->icsk_mtup.probe_timestamp
and arming the close timeout timer.
The comment in mptcp_retry_check_tout() notes "A join stops it", but when the
outgoing retry subflow receives SYN+ACK and subflow_finish_connect() calls
mptcp_finish_join(ssk), subflow->node is already in msk->conn_list, so
mptcp_finish_join() takes the early return path without calling
__mptcp_finish_join() or mptcp_stop_tout_timer(sk):
net/mptcp/protocol.c:mptcp_finish_join() {
...
if (!list_empty(&subflow->node)) {
spin_lock_bh(&msk->fallback_lock);
if (!msk->allow_subflows) {
spin_unlock_bh(&msk->fallback_lock);
return false;
}
mptcp_subflow_joined(msk, ssk);
spin_unlock_bh(&msk->fallback_lock);
mptcp_propagate_sndbuf(parent, ssk);
return true;
}
}
Later, when the 4th ACK arrives in check_fully_established() ->
__mptcp_subflow_fully_established(), mptcp_stop_tout_timer(sk) is not called
there either.
Because inet_csk(sk)->icsk_mtup.probe_timestamp remains non-zero, won't
mptcp_worker() see mptcp_close_tout_expired(sk) as true once close_timeout
elapses and abort the recovered connection with mptcp_do_fastclose(sk) and
__mptcp_close_ssk() (also leaving msk->pm.extra_subflows incremented)?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261025134909.2794368-1-anilkaushikwireless@gmail.com?part=4
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH mptcp-next v9 4/6] mptcp: pm: in-kernel: retry subflows closed after an error
2026-10-25 13:49 ` [PATCH mptcp-next v9 4/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
2026-10-25 14:21 ` sashiko-bot
@ 2026-10-27 3:28 ` netdev-bot+sashiko
1 sibling, 0 replies; 12+ messages in thread
From: netdev-bot+sashiko @ 2026-10-27 3:28 UTC (permalink / raw)
To: anilkaushikwireless; +Cc: mptcp, kuba
Thank you for your contribution! Sashiko AI review found 2 potential
issue(s) to consider.
Critical: 0 · High: 1 · Medium: 1 · Low: 0
If you believe none of the issues are legitimate, please reply to each
issue of Medium severity or higher and explain why the AI is wrong.
If any of them are legitimate and you plan to respin, please let patchwork
know by including "pw-bot: cr" as a separate line at the end of your reply
(one such reply per series is enough).
- [High] The close timeout is armed again when a subflow is re-created,
and nothing cancels it once that subflow connects.
- [Medium] mptcp: pm: retry subflows keep half-closed sockets open when
all subflows close
--
mptcp: pm: in-kernel: retry subflows closed after an error
With this patch, the in-kernel PM re-creates an established subflow that
this side initiated, once TCP gives up on it after a retransmission or
keepalive timeout. The subflow-retries limit is used as the new subflow's
SYN retries. When no other subflow can send, the close timeout is armed
while the re-created subflow connects. Re-created subflows that are still
connecting are closed together with the MPTCP socket.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/440
> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> index 02a4f479d9d8c..25fd0628686c3 100644
> --- a/net/mptcp/protocol.c
> +++ b/net/mptcp/protocol.c
[ ... ]
> @@ -2788,6 +2791,32 @@ static void __mptcp_close_ssk(struct sock *sk, struct sock *ssk,
> }
> }
>
> +/* With no subflow left to send data, a re-created subflow still connecting
> + * must not keep the connection open longer than the close timeout, as when
> + * all the subflows are closed, see __mptcp_close_ssk(). A join stops it.
> + */
> +static void mptcp_retry_check_tout(struct sock *sk)
> +{
> + struct mptcp_subflow_context *subflow;
> + struct mptcp_sock *msk = mptcp_sk(sk);
> + bool connecting = false;
> +
> + if (sk->sk_state != TCP_ESTABLISHED ||
> + inet_csk(sk)->icsk_mtup.probe_timestamp)
> + return;
> +
> + mptcp_for_each_subflow(msk, subflow) {
> + if (__mptcp_subflow_active(subflow))
> + return;
> +
> + connecting |= subflow->retry &&
> + !READ_ONCE(subflow->fully_established);
> + }
> +
> + if (connecting)
> + mptcp_start_tout_timer(sk);
> +}
[Severity: Medium]
Can this early return leave a half-closed msk open for the whole SYN
retry period of a re-created subflow?
Take a connection with two subflows. The first one times out while the
msk is TCP_ESTABLISHED. __mptcp_close_subflow() then re-creates it
through mptcp_pm_subflow_retry(), in TCP_SYN_SENT, with
icsk_syn_retries set from subflow-retries (127 by default). The second
subflow is still active, so mptcp_retry_check_tout() does not arm the
close timeout. That part is fine.
The msk can then leave TCP_ESTABLISHED before close() is called:
- mptcp_check_data_fin() moves it to TCP_CLOSE_WAIT when the peer
sends a DATA_FIN.
- shutdown(SHUT_WR) moves it to TCP_FIN_WAIT1 or TCP_LAST_ACK in
mptcp_shutdown(). If data is still pending,
mptcp_check_send_data_fin() returns before mptcp_subflow_shutdown()
is called, so the connecting subflow is not touched.
After that, mptcp_is_fully_established() is false, and
mptcp_finish_join() would reset the re-created subflow with
MPTCP_RST_EMPTCP. It can no longer carry data. It still stays on
conn_list, because mptcp_close_retry_subflows() is only called from
__mptcp_close().
When the second subflow closes later, this check at the end of
__mptcp_close_ssk() is false:
if (list_is_singular(&msk->conn_list) && msk->first &&
inet_sk_state_load(msk->first) == TCP_CLOSE) {
msk->first and the re-created subflow are both still on the list, so
the msk is not moved to TCP_CLOSE and mptcp_close_wake_up() is not
called. mptcp_retry_check_tout() also returns early here, because
sk_state is not TCP_ESTABLISHED. So the close timeout is not armed
either.
Would the msk then stay half-closed until the re-created subflow gets
an answer, or until TCP gives up on its SYN retries? With the default
limit that is about 4 hours, and the path has just failed, so a quick
answer seems unlikely. An application waiting for the connection to
finish closing would be stuck for that long. That covers both waiting
after shutdown(SHUT_WR) and waiting after reading the peer's EOF.
What is the right place to handle this? One option is to close the
re-created subflows that are still connecting as soon as the msk
leaves TCP_ESTABLISHED, as mptcp_close_retry_subflows() does on
close(). Another is for the "all subflows closed" check in
__mptcp_close_ssk() to ignore them.
[Severity: High]
Is the "A join stops it." part of the comment above true for the
re-created subflow?
On success, __mptcp_subflow_connect() stops the timer. But
__mptcp_close_subflow() calls mptcp_retry_check_tout() right after:
mptcp_pm_subflow_retry(msk, &retry);
/* creating a subflow stopped the close timeout */
mptcp_retry_check_tout(sk);
At this point probe_timestamp is 0 and the old subflow is TCP_CLOSE. The
new subflow has request_join set but not fully_established. So
__mptcp_subflow_active() is false for every subflow, and
mptcp_start_tout_timer() arms the timer again.
The same thing happens through mptcp_close_ssk()->mptcp_retry_check_tout()
when the last active subflow closes while a re-created one is still
connecting.
When the SYN-ACK arrives, subflow_finish_connect()->mptcp_finish_join()
takes the active subflow branch, because the subflow is already on
conn_list:
if (!list_empty(&subflow->node)) {
spin_lock_bh(&msk->fallback_lock);
...
mptcp_subflow_joined(msk, ssk);
spin_unlock_bh(&msk->fallback_lock);
mptcp_propagate_sndbuf(parent, ssk);
return true;
}
This branch never reaches __mptcp_finish_join(), which is the only place a
join calls mptcp_stop_tout_timer().
Does probe_timestamp then stay set after the re-created subflow is
established? mptcp_close_tout_expired() only checks probe_timestamp,
sk_state and the elapsed time. So after close_timeout, mptcp_worker() would
do:
mptcp_do_fastclose(sk);
mptcp_for_each_subflow_safe(msk, subflow, tmp)
__mptcp_close_ssk(sk, subflow->tcp_sock, subflow, 0);
Would this fast-close a connection that has just recovered through the
re-created subflow? One example is a single-path client after an outage
longer than tcp_retries2.
That seems to contradict the commit message, and mptcp.rst says the same
thing:
If no other subflow can send data, the connection is still closed after
the close timeout, as when all the subflows are closed, unless the new
subflow connects before.
There is also a race to consider in a fix. mptcp_retry_check_tout() reads
fully_established holding only the msk socket lock, while the receive path
can set it at the same time. If a stop is added only when the subflow gets
established, could it run before the timer is armed from a stale
fully_established value? Should the expiry path also check whether a
subflow can send again?
The later patches in the series do not change net/. The selftests in
"selftests: mptcp: join: validate subflow retry after link failure" appear
to cover only two cases: another subflow stays alive, or the re-created
subflow never connects.
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261025134909.2794368-1-anilkaushikwireless%40gmail.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH mptcp-next v9 5/6] selftests: mptcp: pm_nl_ctl: support the subflow-retries limit
2026-10-25 13:49 [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
` (3 preceding siblings ...)
2026-10-25 13:49 ` [PATCH mptcp-next v9 4/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
@ 2026-10-25 13:49 ` Anil Kaushik
2026-10-25 13:49 ` [PATCH mptcp-next v9 6/6] selftests: mptcp: join: validate subflow retry after link failure Anil Kaushik
2026-10-25 15:07 ` [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error MPTCP CI
6 siblings, 0 replies; 12+ messages in thread
From: Anil Kaushik @ 2026-10-25 13:49 UTC (permalink / raw)
To: mptcp; +Cc: Anil Kaushik
'pm_nl_ctl limits' can now set the subflow-retries limit with a third
value, and shows it when the kernel supports it.
pm_netlink.sh checks its default value, that a value above the maximum
is refused, and that it can be set. This is only done with pm_nl_ctl
for the moment: iproute2 does not support this limit yet.
Assisted-by: LLM
Signed-off-by: Anil Kaushik <anilkaushikwireless@gmail.com>
---
Notes:
v9:
- try the value above the maximum after setting 0, not the default
value, which is also the maximum: a refused value is then told
apart from a clamped one (netdev Sashiko)
v8:
- the default value is now 127
v7:
- also check that the maximum value, 127, is accepted (netdev
Sashiko)
v5:
- new (Matthieu)
.../testing/selftests/net/mptcp/pm_netlink.sh | 48 ++++++++++++++++++-
tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 34 ++++++++++---
2 files changed, 73 insertions(+), 9 deletions(-)
diff --git a/tools/testing/selftests/net/mptcp/pm_netlink.sh b/tools/testing/selftests/net/mptcp/pm_netlink.sh
index 21bfe1311f11..9a6209181962 100755
--- a/tools/testing/selftests/net/mptcp/pm_netlink.sh
+++ b/tools/testing/selftests/net/mptcp/pm_netlink.sh
@@ -46,15 +46,20 @@ trap cleanup EXIT
mptcp_lib_ns_init ns1
+# $3: subflow retries, only shown by pm_nl_ctl, if supported
format_limits() {
local accept="${1}"
local subflows="${2}"
+ local retries="${3}"
if mptcp_lib_is_ip_mptcp; then
# with a space at the end
printf "add_addr_accepted %d subflows %d \n" "${accept}" "${subflows}"
else
printf "accept %d\nsubflows %d\n" "${accept}" "${subflows}"
+ if [ -n "${retries}" ]; then
+ printf "subflow_retries %d\n" "${retries}"
+ fi
fi
}
@@ -75,6 +80,22 @@ get_limits_nb() {
fi
}
+# The subflow retries limit is only set and shown with pm_nl_ctl for now.
+# Prints its default value if it is supported.
+get_default_retries() {
+ if mptcp_lib_is_ip_mptcp; then
+ return
+ fi
+
+ if ip netns exec "${ns1}" ./pm_nl_ctl limits |
+ grep -q "^subflow_retries"; then
+ echo 127
+ elif mptcp_lib_expect_all_features; then
+ # missing feature: the defaults limits check will fail
+ echo 127
+ fi
+}
+
format_endpoints() {
mptcp_lib_pm_nl_format_endpoints "${@}"
}
@@ -154,8 +175,10 @@ mptcp_lib_subtests_last_ts_reset
check "show_endpoints" "" "defaults addr list"
default_limits="$(get_limits)"
+default_retries="$(get_default_retries)"
if mptcp_lib_expect_all_features; then
- check "get_limits" "$(format_limits 0 2)" "defaults limits"
+ check "get_limits" "$(format_limits 0 2 "${default_retries}")" \
+ "defaults limits"
fi
add_endpoint 10.0.1.1
@@ -224,7 +247,28 @@ check "get_limits" "${default_limits}" "subflows above hard limit"
set_limits ${max_limits} ${max_limits}
flush_endpoint ## to make sure it doesn't affect the limits
-check "get_limits" "$(format_limits ${max_limits} ${max_limits})" "set limits"
+max_limits_out="$(format_limits ${max_limits} ${max_limits} \
+ "${default_retries}")"
+check "get_limits" "${max_limits_out}" "set limits"
+
+if [ -n "${default_retries}" ]; then
+ ip netns exec "${ns1}" ./pm_nl_ctl limits ${max_limits} ${max_limits} 0
+ check "get_limits" "$(format_limits ${max_limits} ${max_limits} 0)" \
+ "set subflow retries"
+
+ # not from the default: a refused value differs from a clamped one
+ ip netns exec "${ns1}" ./pm_nl_ctl limits ${max_limits} ${max_limits} \
+ 128 2>/dev/null
+ check "get_limits" "$(format_limits ${max_limits} ${max_limits} 0)" \
+ "subflow retries above hard limit"
+
+ ip netns exec "${ns1}" ./pm_nl_ctl limits ${max_limits} ${max_limits} \
+ 127
+ check "get_limits" "$(format_limits ${max_limits} ${max_limits} 127)" \
+ "set max subflow retries"
+ ip netns exec "${ns1}" ./pm_nl_ctl limits ${max_limits} ${max_limits} \
+ "${default_retries}"
+fi
flush_endpoint
add_endpoint 10.0.1.1
diff --git a/tools/testing/selftests/net/mptcp/pm_nl_ctl.c b/tools/testing/selftests/net/mptcp/pm_nl_ctl.c
index 78180da1efcc..41467b997018 100644
--- a/tools/testing/selftests/net/mptcp/pm_nl_ctl.c
+++ b/tools/testing/selftests/net/mptcp/pm_nl_ctl.c
@@ -39,7 +39,7 @@ static void syntax(char *argv[])
fprintf(stderr, "\tset [<ip>] [id <nr>] flags [no]backup|[no]fullmesh [port <nr>] [token <token>] [rip <ip>] [rport <port>]\n");
fprintf(stderr, "\tflush\n");
fprintf(stderr, "\tdump\n");
- fprintf(stderr, "\tlimits [<rcv addr max> <subflow max>]\n");
+ fprintf(stderr, "\tlimits [<rcv addr max> <subflow max> [<retry>]]\n");
fprintf(stderr, "\tevents\n");
fprintf(stderr, "\tlisten <local-ip> <local-port>\n");
exit(0);
@@ -1217,6 +1217,7 @@ int flush_addrs(int fd, int pm_family, int argc, char *argv[])
static void print_limits(struct nlmsghdr *nh, int pm_family, int total_len)
{
struct rtattr *attrs;
+ const char *name;
uint32_t max;
for (; NLMSG_OK(nh, total_len); nh = NLMSG_NEXT(nh, total_len)) {
@@ -1235,13 +1236,22 @@ static void print_limits(struct nlmsghdr *nh, int pm_family, int total_len)
while (RTA_OK(attrs, len)) {
int type = attrs->rta_type;
- if (type != MPTCP_PM_ATTR_RCV_ADD_ADDRS &&
- type != MPTCP_PM_ATTR_SUBFLOWS)
+ switch (type) {
+ case MPTCP_PM_ATTR_RCV_ADD_ADDRS:
+ name = "accept";
+ break;
+ case MPTCP_PM_ATTR_SUBFLOWS:
+ name = "subflows";
+ break;
+ case MPTCP_PM_ATTR_SUBFLOW_RETRIES:
+ name = "subflow_retries";
+ break;
+ default:
goto next;
+ }
memcpy(&max, RTA_DATA(attrs), 4);
- printf("%s %u\n", type == MPTCP_PM_ATTR_SUBFLOWS ?
- "subflows" : "accept", max);
+ printf("%s %u\n", name, max);
next:
attrs = RTA_NEXT(attrs, len);
@@ -1254,15 +1264,17 @@ int get_set_limits(int fd, int pm_family, int argc, char *argv[])
char data[NLMSG_ALIGN(sizeof(struct nlmsghdr)) +
NLMSG_ALIGN(sizeof(struct genlmsghdr)) +
1024];
- uint32_t rcv_addr = 0, subflows = 0;
+ uint32_t rcv_addr = 0, subflows = 0, retries = 0;
int cmd, len = sizeof(data);
struct nlmsghdr *nh;
int off = 0;
/* limit */
- if (argc == 4) {
+ if (argc == 4 || argc == 5) {
rcv_addr = atoi(argv[2]);
subflows = atoi(argv[3]);
+ if (argc == 5)
+ retries = atoi(argv[4]);
cmd = MPTCP_PM_CMD_SET_LIMITS;
} else {
cmd = MPTCP_PM_CMD_GET_LIMITS;
@@ -1287,6 +1299,14 @@ int get_set_limits(int fd, int pm_family, int argc, char *argv[])
memcpy(RTA_DATA(rta), &subflows, 4);
off += NLMSG_ALIGN(rta->rta_len);
+ if (argc == 5) {
+ rta = (void *)(data + off);
+ rta->rta_type = MPTCP_PM_ATTR_SUBFLOW_RETRIES;
+ rta->rta_len = RTA_LENGTH(4);
+ memcpy(RTA_DATA(rta), &retries, 4);
+ off += NLMSG_ALIGN(rta->rta_len);
+ }
+
/* do not expect a reply */
len = 0;
}
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH mptcp-next v9 6/6] selftests: mptcp: join: validate subflow retry after link failure
2026-10-25 13:49 [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
` (4 preceding siblings ...)
2026-10-25 13:49 ` [PATCH mptcp-next v9 5/6] selftests: mptcp: pm_nl_ctl: support the subflow-retries limit Anil Kaushik
@ 2026-10-25 13:49 ` Anil Kaushik
2026-10-27 3:28 ` netdev-bot+sashiko
2026-10-25 15:07 ` [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error MPTCP CI
6 siblings, 1 reply; 12+ messages in thread
From: Anil Kaushik @ 2026-10-25 13:49 UTC (permalink / raw)
To: mptcp; +Cc: Anil Kaushik
Test the subflow-retries limit, with its default value, and a long
connection in the background: drop the packets the client sends from
the additional subflow address with netfilter, without bringing the link
down, until the subflow is closed and re-created. Let them through again
once the SYN of the new subflow has been retransmitted more times than
tcp_syn_retries allows, and check the subflow comes back from the same
address. Then do the same with the initial subflow.
A second test closes the connection while a subflow is being re-created,
and checks the netlink events. Only the client sends data: the server
reads it all first, in sendfile mode, and keeps its side open. The
client gets a big MPTCP send buffer compared to its subflows, and both
paths are blocked: the data left in it is never sent, nor the DATA_FIN,
so only the close of the MPTCP socket can stop the subflow being
re-created. Only the client is closed: it has nothing left to read, so
the connection is not closed with a fastclose, which would reset all the
subflows anyway. The check is skipped if a fastclose happens. The big
files used for the long connection are emptied at the end.
A third test re-creates the only subflow, and checks the connection is
still closed after the close timeout, the new subflow being unable to
connect.
The tests are skipped if pm_nl_ctl does not show the new limit, or if the
filter rules cannot be set.
Assisted-by: LLM
Signed-off-by: Anil Kaushik <anilkaushikwireless@gmail.com>
---
Notes:
v9:
- wait for absolute counter values, read before blocking the path,
or 0 and 1 in the new netns: the subflow can be re-created before
a later read (netdev Sashiko)
- check that the connection is established before blocking it, in
the close test and the new one (netdev Sashiko)
- the close test blocks the other path too, with a big msk send
buffer: the pending data and the DATA_FIN no longer close the
subflow being re-created, only the close of the MPTCP socket can.
Checked: both the close test and the new test fail without their
fix
- new test: the only subflow is re-created, and the connection is
still closed after the close timeout
- $sinfail as the server input, kill errors ignored, clearer failure
message, $cout and $sout emptied too
- the server of the second test reads all the data from the client
first, in sendfile mode, instead of blocking on a FIFO in poll
mode: the client always has data in flight (netdev Sashiko)
v8:
- comment in run_tests() matching the new condition (netdev Sashiko)
- a separate test closes the connection while a subflow is
re-created: the server sends nothing but keeps its side open, and
only the client is closed, so there is no fastclose, which would
reset all the subflows anyway; the check is skipped if one happens
(netdev Sashiko)
v7 (netdev Sashiko):
- the test_linkfail=1/2 modes regenerate the shared files when they
are empty, e.g. when running link_failure_tests() twice
- read the MP_JOIN ACK counter before letting the packets through,
and do not compare the ports, they can be reused
v6 (Sashiko):
- use the slowwait helpers from net/lib.sh
- longer first wait, while the 128 MB files are created
- skip if the filter rules cannot be set, check each drop rule
(netdev Sashiko)
- empty the big files at the end, cinsent too, keep the variables
(netdev Sashiko)
v5 (Matthieu):
- skipped if pm_nl_ctl does not show the new limit
- wait for the SYN retransmissions instead of a sleep, with
tcp_syn_linear_timeouts=0
- helper for the check after the close
- slower links with short queues, so the transfer lasts the whole
test on any machine, longer timeout (killed at the end)
v4:
- default limit, no sysctl or MIB counter
- more SYN retransmissions than tcp_syn_retries
- close the connection while a subflow is re-created
- check the netlink events
- check the waits and the new subflow port, remove the big files at
the end (Sashiko)
v3:
- check the subflow address, create the files before the background job
v2:
- one test, with netfilter
.../testing/selftests/net/mptcp/mptcp_join.sh | 328 +++++++++++++++++-
1 file changed, 320 insertions(+), 8 deletions(-)
diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
index c3ccce96b45b..e80f3f5f9997 100755
--- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
+++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
@@ -52,6 +52,7 @@ nr_blank=6
# These var are used only in some tests, make sure they are not already set
unset FAILING_LINKS
unset test_linkfail
+unset server_in
unset addr_nr_ns1
unset addr_nr_ns2
unset cestab_ns1
@@ -1038,7 +1039,12 @@ do_transfer()
fi
extra_srv_args="$extra_args $extra_srv_args"
- if [ "$test_linkfail" -gt 1 ];then
+ if [ -n "${server_in}" ]; then
+ # the server reads all the data from the client before sending
+ # this file: it does not block on its input
+ extra_srv_args="$extra_srv_args -m sendfile"
+ listener_in="${server_in}"
+ elif [ "$test_linkfail" -gt 1 ]; then
listener_in="${sinfail}"
fi
ip netns exec ${listener_ns} \
@@ -1135,9 +1141,9 @@ run_tests()
cinfail=$(mktemp)
fi
make_file "$cinfail" "client" $size
- # create the input file for the failure test when
- # the first failure test run
- elif [ "$test_linkfail" -ne 0 ] && [ -z "$cinfail" ]; then
+ # create the input file for the failure test, when
+ # it is missing or has been emptied
+ elif [ "$test_linkfail" -ne 0 ] && [ ! -s "$cinfail" ]; then
# the client file must be considerably larger
# of the maximum expected cwin value, or the
# link utilization will be not predicable
@@ -1146,23 +1152,27 @@ run_tests()
size=$((size*8192))
size=$((size + ( RANDOM % 8192) ))
- cinfail=$(mktemp)
+ if [ -z "$cinfail" ]; then
+ cinfail=$(mktemp)
+ fi
make_file "$cinfail" "client" $size
fi
- if [ "$test_linkfail" -gt 2 ]; then
+ if [ "$test_linkfail" -gt 2 ] && [ -z "${server_in}" ]; then
size=$test_linkfail
if [ -z "$sinfail" ]; then
sinfail=$(mktemp)
fi
make_file "$sinfail" "server" $size
- elif [ "$test_linkfail" -eq 2 ] && [ -z "$sinfail" ]; then
+ elif [ "$test_linkfail" -eq 2 ] && [ ! -s "$sinfail" ]; then
size=$((RANDOM%16))
size=$((size+1))
size=$((size*2048))
- sinfail=$(mktemp)
+ if [ -z "$sinfail" ]; then
+ sinfail=$(mktemp)
+ fi
make_file "$sinfail" "server" $size
fi
@@ -2151,6 +2161,195 @@ wait_attempt_fail()
return 1
}
+# $1: timeout in seconds ; $2: ns ; $3: counter ; $4: increment, 1 by default
+wait_counter_inc()
+{
+ slowwait_for_counter "${1}" "${4:-1}" \
+ mptcp_lib_get_counter "${2}" "${3}" >/dev/null
+}
+
+# $1: timeout ; $2: ns ; $3: counter ; $4: value to reach
+wait_counter_ge()
+{
+ slowwait "${1}" until_counter_is ">= ${4}" \
+ mptcp_lib_get_counter "${2}" "${3}" >/dev/null
+}
+
+# $1: client address ; prints the local address and port of its subflow
+sf_from()
+{
+ ip netns exec $ns2 ss -tnH state established src "${1}" |
+ awk '{ print $3; exit }'
+}
+
+has_subflow_retries()
+{
+ ip netns exec $ns2 ./pm_nl_ctl limits | grep -q "^subflow_retries"
+}
+
+# the client packets are dropped with rules in this chain
+init_nft_filter()
+{
+ init_nftables
+ if ! ip netns exec $ns2 nft list chain ip filter OUTPUT \
+ &>/dev/null; then
+ mark_as_skipped "unable to set the filter rules"
+ return 1
+ fi
+}
+
+# $1: client address
+nft_drop_from()
+{
+ ip netns exec $ns2 nft add rule ip filter OUTPUT ip saddr "${1}" drop
+}
+
+# $1: client address to block
+#
+# The link stays up, but the client packets from this address are dropped:
+# the subflow using it is closed after a few retransmissions, and re-created.
+# The packets go through again once the SYN has been retransmitted more times
+# than tcp_syn_retries allows: the new subflow still connects thanks to the
+# subflow-retries limit.
+sf_retry_after_block()
+{
+ local before ack_rx syn_tx
+
+ before=$(sf_from "${1}")
+
+ print_check "subflow from ${1}"
+ if [ -z "${before}" ]; then
+ fail_test "no established subflow from ${1} before the block"
+ return
+ fi
+
+ # read before the block: the subflow can be re-created right after it
+ syn_tx=$(mptcp_lib_get_counter $ns2 "MPTcpExtMPJoinSynTx")
+ if ! nft_drop_from "${1}"; then
+ fail_test "unable to drop the packets from ${1}"
+ return
+ fi
+ if ! wait_counter_ge "${timeout_poll}" $ns2 "MPTcpExtMPJoinSynTx" \
+ $((syn_tx + 1)); then
+ ip netns exec $ns2 nft flush chain ip filter OUTPUT
+ fail_test "subflow from ${1} not re-created"
+ return
+ fi
+ # tcp_syn_retries=1: one more retransmission than allowed
+ if ! wait_counter_inc "${timeout_poll}" \
+ $ns2 "TcpExtTCPSynRetrans" 2; then
+ ip netns exec $ns2 nft flush chain ip filter OUTPUT
+ fail_test "SYN from ${1} not retransmitted enough"
+ return
+ fi
+ # read before the flush: the next SYN can be sent right after it
+ ack_rx=$(mptcp_lib_get_counter $ns1 "MPTcpExtMPJoinAckRx")
+ ip netns exec $ns2 nft flush chain ip filter OUTPUT
+
+ if ! wait_counter_ge "${timeout_poll}" $ns1 "MPTcpExtMPJoinAckRx" \
+ $((ack_rx + 1)); then
+ fail_test "re-created subflow from ${1} not established"
+ return
+ fi
+
+ if [ -z "$(sf_from "${1}")" ]; then
+ fail_test "no established subflow from ${1}"
+ else
+ print_ok
+ fi
+}
+
+# $1: ns ; prints the number of MP_FASTCLOSE sent and received
+fastclose_nr()
+{
+ local tx rx
+
+ tx=$(mptcp_lib_get_counter "${1}" "MPTcpExtMPFastcloseTx")
+ rx=$(mptcp_lib_get_counter "${1}" "MPTcpExtMPFastcloseRx")
+ echo $((${tx:-0} + ${rx:-0}))
+}
+
+no_sf_connecting()
+{
+ ! ip netns exec $ns2 ss -tnH state syn-sent | grep -q .
+}
+
+# The client has nothing left to read: it closes the connection without a
+# fastclose, which would reset all the subflows anyway.
+kill_client()
+{
+ local pid
+
+ for pid in $(ip netns pids $ns2); do
+ if [ "$(cat "/proc/${pid}/comm" 2>/dev/null)" = mptcp_connect ]
+ then
+ kill "${pid}" 2>/dev/null
+ fi
+ done
+}
+
+# $1: why the subflow is not being re-created before the close, if it is not
+# $2: number of MP_FASTCLOSE before the close
+chk_no_sf_connecting()
+{
+ local closed
+
+ print_check "no subflow connecting after close"
+ if [ -n "${1}" ]; then
+ fail_test "${1}"
+ return
+ fi
+
+ # closed with the MPTCP socket
+ slowwait "${timeout_poll}" no_sf_connecting
+ closed=$?
+ if [ "$(fastclose_nr $ns2)" -gt "${2}" ]; then
+ print_skip "closed with a fastclose, resetting all the subflows"
+ elif [ "${closed}" -eq 0 ]; then
+ print_ok
+ else
+ fail_test "subflow still connecting after close"
+ fi
+}
+
+# Slow links with short queues: the transfer lasts the whole test on any
+# machine, and the blocked subflow always has data in flight.
+sf_retry_init()
+{
+ local i
+
+ for i in 1 3; do
+ tc -n $ns1 qdisc add dev ns1eth$i root netem \
+ rate 4mbit limit 30 delay 1ms
+ tc -n $ns2 qdisc add dev ns2eth$i root netem \
+ rate 4mbit limit 30 delay 1ms
+ done
+ ip netns exec $ns2 sysctl -q net.ipv4.tcp_retries2=3
+ ip netns exec $ns2 sysctl -q net.ipv4.tcp_syn_retries=1
+ ip netns exec $ns2 sysctl -q net.ipv4.tcp_syn_linear_timeouts=0
+ pm_nl_set_limits $ns1 0 4
+ pm_nl_set_limits $ns2 0 2
+ pm_nl_add_endpoint $ns2 10.0.3.2 dev ns2eth3 flags subflow
+ # created here, not in the background job, for cleanup()
+ if [ -z "$cinfail" ]; then
+ cinfail=$(mktemp)
+ fi
+ if [ -z "$sinfail" ]; then
+ sinfail=$(mktemp)
+ fi
+}
+
+sf_retry_cleanup()
+{
+ ip netns exec $ns2 nft flush chain ip filter OUTPUT
+ # big files: empty them, the next tests write their own content
+ : > "$cinfail"
+ : > "$sinfail"
+ : > "$cinsent"
+ : > "$cout"
+ : > "$sout"
+}
+
set_userspace_pm()
{
local ns=$1
@@ -2585,6 +2784,119 @@ link_failure_tests()
chk_stale_nr $ns2 1 -1 2
chk_link_usage $ns2 ns2eth3 $cinsent 50
fi
+
+ # subflows closed after a silent link failure, then re-created: the
+ # additional one, then the initial one
+ if reset_with_events "subflow retry after link failure" &&
+ continue_if has_subflow_retries && init_nft_filter; then
+ sf_retry_init
+ # killed at the end: the timeout only stops a stuck test
+ { timeout_test=600 test_linkfail=131072 \
+ run_tests $ns1 $ns2 10.0.1.1 & } 2>/dev/null
+ local tests_pid=$!
+
+ # the 128 MB files are created first, that can take a while
+ wait_counter_ge $((timeout_poll * 4)) \
+ $ns1 "MPTcpExtMPJoinAckRx" 1
+ sf_retry_after_block 10.0.3.2
+ sf_retry_after_block 10.0.1.2
+ mptcp_lib_kill_group_wait $tests_pid
+ kill_events_pids
+
+ join_syn_tx=3 chk_join_nr 3 3 3
+ chk_evt_nr ns2 MPTCP_LIB_EVENT_SUB_ESTABLISHED 3
+ chk_evt_nr ns2 MPTCP_LIB_EVENT_SUB_CLOSED 2 error 2
+ sf_retry_cleanup
+ fi
+
+ # close the connection while a subflow is being re-created
+ if reset_with_events "subflow retry, close while connecting" &&
+ continue_if has_subflow_retries && init_nft_filter; then
+ sf_retry_init
+ # A big msk send buffer, compared to the subflow ones: when the
+ # client is closed, some data is not given to any subflow yet,
+ # so the DATA_FIN, which would also close the subflow being
+ # re-created, is not sent.
+ ip netns exec $ns2 sysctl -q \
+ net.ipv4.tcp_wmem="1048576 65536 262144"
+ # The server reads until the client closes, and sends nothing:
+ # the client has nothing to read, and the connection stays
+ # established. The transfer is stopped on purpose, its result
+ # is not checked.
+ : > "$sinfail"
+ { timeout_test=600 test_linkfail=131072 server_in="$sinfail" \
+ run_tests $ns1 $ns2 10.0.1.1 >/dev/null & } 2>/dev/null
+ local tests_pid=$!
+
+ local not_ready="" syn_tx
+ if ! wait_counter_ge $((timeout_poll * 4)) \
+ $ns1 "MPTcpExtMPJoinAckRx" 1; then
+ not_ready="no additional subflow before the block"
+ else
+ # read before the block: the subflow can be re-created
+ # right after it
+ syn_tx=$(mptcp_lib_get_counter $ns2 \
+ "MPTcpExtMPJoinSynTx")
+ if ! nft_drop_from 10.0.3.2; then
+ not_ready="unable to drop the packets"
+ elif ! wait_counter_ge "${timeout_poll}" \
+ $ns2 "MPTcpExtMPJoinSynTx" $((syn_tx + 1)); then
+ not_ready="no subflow re-created before close"
+ fi
+ fi
+ # Block the other path too, so this data is never sent: only
+ # the close of the MPTCP socket can then stop the subflow being
+ # re-created.
+ if [ -z "${not_ready}" ] && ! nft_drop_from 10.0.1.2; then
+ not_ready="unable to drop the packets"
+ fi
+ local fc_before
+ fc_before=$(fastclose_nr $ns2)
+ kill_client
+ chk_no_sf_connecting "${not_ready}" "${fc_before}"
+ mptcp_lib_kill_group_wait $tests_pid
+ kill_events_pids
+
+ join_syn_tx=2 chk_join_nr 1 1 1
+ chk_evt_nr ns2 MPTCP_LIB_EVENT_SUB_ESTABLISHED 1
+ chk_evt_nr ns2 MPTCP_LIB_EVENT_SUB_CLOSED 1 error 1
+ sf_retry_cleanup
+ fi
+
+ # the only subflow is re-created: the connection is still closed after
+ # the close timeout, the new subflow cannot connect
+ if reset_with_events "subflow retry, no other subflow" &&
+ continue_if has_subflow_retries && init_nft_filter; then
+ sf_retry_init
+ pm_nl_flush_endpoint $ns2
+ ip netns exec $ns2 sysctl -q net.mptcp.close_timeout=5
+ { timeout_test=600 test_linkfail=131072 \
+ run_tests $ns1 $ns2 10.0.1.1 >/dev/null & } 2>/dev/null
+ local tests_pid=$!
+
+ print_check "closed after the close timeout"
+ if ! wait_counter_ge $((timeout_poll * 4)) \
+ $ns1 "MPTcpExtMPCapableACKRX" 1; then
+ fail_test "connection not established"
+ elif ! nft_drop_from 10.0.1.2; then
+ fail_test "unable to drop the packets"
+ # no other subflow: the first MP_JOIN SYN is the re-created one
+ elif ! wait_counter_ge "${timeout_poll}" \
+ $ns2 "MPTcpExtMPJoinSynTx" 1; then
+ fail_test "no subflow re-created"
+ # closed with the connection, after 5 seconds
+ elif slowwait "${timeout_poll}" no_sf_connecting; then
+ print_ok
+ else
+ fail_test "subflow still connecting"
+ fi
+ mptcp_lib_kill_group_wait $tests_pid
+ kill_events_pids
+
+ join_syn_tx=1 chk_join_nr 0 0 0
+ chk_evt_nr ns2 MPTCP_LIB_EVENT_SUB_CLOSED 1 error 1
+ sf_retry_cleanup
+ fi
}
add_addr_timeout_tests()
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread* Re: [PATCH mptcp-next v9 6/6] selftests: mptcp: join: validate subflow retry after link failure
2026-10-25 13:49 ` [PATCH mptcp-next v9 6/6] selftests: mptcp: join: validate subflow retry after link failure Anil Kaushik
@ 2026-10-27 3:28 ` netdev-bot+sashiko
0 siblings, 0 replies; 12+ messages in thread
From: netdev-bot+sashiko @ 2026-10-27 3:28 UTC (permalink / raw)
To: anilkaushikwireless; +Cc: mptcp, kuba
Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider.
Critical: 0 · High: 0 · Medium: 1 · Low: 0
If you believe none of the issues are legitimate, please reply to each
issue of Medium severity or higher and explain why the AI is wrong.
If any of them are legitimate and you plan to respin, please let patchwork
know by including "pw-bot: cr" as a separate line at the end of your reply
(one such reply per series is enough).
- [Medium] In link_failure_tests(), the third new test ("subflow retry,
no other subflow") does not reliably check what it claims, that the…
--
selftests: mptcp: join: validate subflow retry after link failure
This adds three tests to link_failure_tests() for the subflow-retries
limit. Netfilter drops the client packets so the subflows are closed and
re-created. The tests check that the re-created subflows connect again,
that a subflow still connecting goes away when the connection is closed,
and that a connection whose only subflow is re-created is still closed
after the close timeout.
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index c3ccce96b45b1..e80f3f5f99973 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
[ ... ]
> @@ -2585,6 +2784,119 @@ link_failure_tests()
[ ... ]
> + # the only subflow is re-created: the connection is still closed after
> + # the close timeout, the new subflow cannot connect
> + if reset_with_events "subflow retry, no other subflow" &&
> + continue_if has_subflow_retries && init_nft_filter; then
> + sf_retry_init
> + pm_nl_flush_endpoint $ns2
> + ip netns exec $ns2 sysctl -q net.mptcp.close_timeout=5
> + { timeout_test=600 test_linkfail=131072 \
> + run_tests $ns1 $ns2 10.0.1.1 >/dev/null & } 2>/dev/null
> + local tests_pid=$!
> +
> + print_check "closed after the close timeout"
> + if ! wait_counter_ge $((timeout_poll * 4)) \
> + $ns1 "MPTcpExtMPCapableACKRX" 1; then
> + fail_test "connection not established"
> + elif ! nft_drop_from 10.0.1.2; then
> + fail_test "unable to drop the packets"
> + # no other subflow: the first MP_JOIN SYN is the re-created one
> + elif ! wait_counter_ge "${timeout_poll}" \
> + $ns2 "MPTcpExtMPJoinSynTx" 1; then
> + fail_test "no subflow re-created"
> + # closed with the connection, after 5 seconds
> + elif slowwait "${timeout_poll}" no_sf_connecting; then
> + print_ok
[Severity: Medium]
Could this check pass even when the close timeout never fires?
do_transfer() starts the background client with the usual 30 s I/O
timeout. Setting timeout_test=600 only changes the outer watchdog:
./mptcp_connect -t ${timeout_poll} -p $port -s ${cl_proto} \
After 10.0.1.2 is blocked, the client gets no more events. When poll()
times out, copyfd_io_poll() returns 2 and mptcp_connect exits, which
closes the MPTCP socket. __mptcp_close() then calls
mptcp_close_retry_subflows(), and that closes the SYN_SENT retry subflow
without any help from the close timeout:
net/mptcp/protocol.c:mptcp_close_retry_subflows() {
...
if (state != TCP_SYN_SENT && state != TCP_CLOSE)
continue;
...
__mptcp_close_ssk(sk, ssk, subflow, 0);
}
The client's last event happens at or before the re-created SYN. Its 30 s
poll timeout therefore starts around the time of the block.
The slowwait window here is also timeout_poll (30 s). It only starts once
MPTcpExtMPJoinSynTx >= 1 is seen, about 3-5 s after the block with
tcp_retries2=3. So the client's own close falls inside this window, or
races with its end.
Suppose the re-arm in mptcp_retry_check_tout() were missing or broken:
if (connecting)
mptcp_start_tout_timer(sk);
__mptcp_subflow_connect() stops the timer, so the subflow would stay
connecting until the client exits on its own. Wouldn't this check still
print ok, or pass or fail depending on a sub-second race?
The final checks don't tell the two close paths apart either.
__mptcp_close_ssk() emits no SUB_CLOSED event, and the exit status of the
background transfer is never checked.
Could the wait be bounded to close_timeout plus a margin, well below
timeout_poll? Alternatively, the test could check that the client is still
running when the subflow goes away.
> + else
> + fail_test "subflow still connecting"
> + fi
> + mptcp_lib_kill_group_wait $tests_pid
> + kill_events_pids
> +
> + join_syn_tx=1 chk_join_nr 0 0 0
> + chk_evt_nr ns2 MPTCP_LIB_EVENT_SUB_CLOSED 1 error 1
> + sf_retry_cleanup
> + fi
> }
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261025134909.2794368-1-anilkaushikwireless%40gmail.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error
2026-10-25 13:49 [PATCH mptcp-next v9 0/6] mptcp: pm: in-kernel: retry subflows closed after an error Anil Kaushik
` (5 preceding siblings ...)
2026-10-25 13:49 ` [PATCH mptcp-next v9 6/6] selftests: mptcp: join: validate subflow retry after link failure Anil Kaushik
@ 2026-10-25 15:07 ` MPTCP CI
6 siblings, 0 replies; 12+ messages in thread
From: MPTCP CI @ 2026-10-25 15:07 UTC (permalink / raw)
To: Anil Kaushik; +Cc: mptcp
Hi Anil,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal (except selftest_mptcp_join): Success! ✅
- KVM Validation: normal (only selftest_mptcp_join): Success! ✅
- KVM Validation: debug (except selftest_mptcp_join): Success! ✅
- KVM Validation: debug (only selftest_mptcp_join): Success! ✅
- KVM Validation: btf-normal (only bpftest_all): Success! ✅
- KVM Validation: btf-debug (only bpftest_all): Success! ✅
- Perf: Unstable ⚠️
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/40200459151
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/65fbacd31d21
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=1193019
If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:
$ cd [kernel source code]
$ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
--pull always mptcp/mptcp-upstream-virtme-docker:latest \
auto-normal
For more details:
https://github.com/multipath-tcp/mptcp-upstream-virtme-docker
Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)
Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)
^ permalink raw reply [flat|nested] 12+ messages in thread