All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors
@ 2023-01-30 16:23 Paolo Abeni
  2023-01-30 17:42 ` mptcp: be careful on subflow status propagation on errors: Tests Results MPTCP CI
  2023-01-31  9:17 ` [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors Matthieu Baerts
  0 siblings, 2 replies; 3+ messages in thread
From: Paolo Abeni @ 2023-01-30 16:23 UTC (permalink / raw)
  To: mptcp

Currently the subflow error report callback unconditionally
propagates the fallback subflow status to the owning msk.

If the msk is already orphaned, the above prevents the code
from correctly tracking the msk moving to the TCP_CLOSE state
and doing the appropriate cleanup.

All the above causes increasing memory usage over time and
sporadic self-tests failures.

There is a great deal of infrastructure trying to propagate
correctly the fallback subflow status to the owning mptcp socket,
e.g. via mptcp_subflow_eof() and subflow_sched_work_if_closed():
in the error propagation path we need only to cope with unorphaned
sockets.

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/339
Fixes: 15cc10453398 ("mptcp: deliver ssk errors to msk")
Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
--
v2 -> v3:
 - cleanup code comment
v1 -> v2:
 - propagate the status for non orphaned sockets
---
 net/mptcp/subflow.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/net/mptcp/subflow.c b/net/mptcp/subflow.c
index 5e57a9a7178b..f075607adad4 100644
--- a/net/mptcp/subflow.c
+++ b/net/mptcp/subflow.c
@@ -1404,6 +1404,7 @@ void __mptcp_error_report(struct sock *sk)
 	mptcp_for_each_subflow(msk, subflow) {
 		struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
 		int err = sock_error(ssk);
+		int ssk_state;
 
 		if (!err)
 			continue;
@@ -1414,7 +1415,14 @@ void __mptcp_error_report(struct sock *sk)
 		if (sk->sk_state != TCP_SYN_SENT && !__mptcp_check_fallback(msk))
 			continue;
 
-		inet_sk_state_store(sk, inet_sk_state_load(ssk));
+		/* We need to propagate only transition to CLOSE state.
+		 * Orphaned socket will see such state change via
+		 * subflow_sched_work_if_closed() and that path will properly
+		 * destroy the msk as needed.
+		 */
+		ssk_state = inet_sk_state_load(ssk);
+		if (ssk_state == TCP_CLOSE && !sock_flag(sk, SOCK_DEAD))
+			inet_sk_state_store(sk, ssk_state);
 		sk->sk_err = -err;
 
 		/* This barrier is coupled with smp_rmb() in mptcp_poll() */
-- 
2.39.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: mptcp: be careful on subflow status propagation on errors: Tests Results
  2023-01-30 16:23 [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors Paolo Abeni
@ 2023-01-30 17:42 ` MPTCP CI
  2023-01-31  9:17 ` [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors Matthieu Baerts
  1 sibling, 0 replies; 3+ messages in thread
From: MPTCP CI @ 2023-01-30 17:42 UTC (permalink / raw)
  To: Paolo Abeni; +Cc: mptcp

Hi Paolo,

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! ✅:
  - Task: https://cirrus-ci.com/task/4854224215867392
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/4854224215867392/summary/summary.txt

- KVM Validation: normal (only selftest_mptcp_join):
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/5980124122710016
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5980124122710016/summary/summary.txt

- KVM Validation: debug (only selftest_mptcp_join):
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/6543074076131328
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/6543074076131328/summary/summary.txt

- KVM Validation: debug (except selftest_mptcp_join):
  - Success! ✅:
  - Task: https://cirrus-ci.com/task/5417174169288704
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5417174169288704/summary/summary.txt

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/390fff044f6c


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-debug

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 (Tessares)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors
  2023-01-30 16:23 [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors Paolo Abeni
  2023-01-30 17:42 ` mptcp: be careful on subflow status propagation on errors: Tests Results MPTCP CI
@ 2023-01-31  9:17 ` Matthieu Baerts
  1 sibling, 0 replies; 3+ messages in thread
From: Matthieu Baerts @ 2023-01-31  9:17 UTC (permalink / raw)
  To: Paolo Abeni, mptcp

Hi Paolo,

On 30/01/2023 17:23, Paolo Abeni wrote:
> Currently the subflow error report callback unconditionally
> propagates the fallback subflow status to the owning msk.
> 
> If the msk is already orphaned, the above prevents the code
> from correctly tracking the msk moving to the TCP_CLOSE state
> and doing the appropriate cleanup.
> 
> All the above causes increasing memory usage over time and
> sporadic self-tests failures.
> 
> There is a great deal of infrastructure trying to propagate
> correctly the fallback subflow status to the owning mptcp socket,
> e.g. via mptcp_subflow_eof() and subflow_sched_work_if_closed():
> in the error propagation path we need only to cope with unorphaned
> sockets.

Thank you for the patch!

Now in our tree (fix for -net):

New patches for t/upstream-net:
- 8db5a7061505: mptcp: be careful on subflow status propagation on errors
- Results: bc024ce64d00..2215d62f4f56 (export-net)
- Results: c8daebf53701..0825e0ffa158 (export)

Tests are now in progress:

https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export-net/20230131T091051
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20230131T091051

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-01-31  9:17 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-30 16:23 [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors Paolo Abeni
2023-01-30 17:42 ` mptcp: be careful on subflow status propagation on errors: Tests Results MPTCP CI
2023-01-31  9:17 ` [PATCH mptcp-net v3] mptcp: be careful on subflow status propagation on errors Matthieu Baerts

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.