From: Paolo Abeni <pabeni@redhat.com>
To: menglong8.dong@gmail.com, mathew.j.martineau@linux.intel.com,
matthieu.baerts@tessares.net
Cc: mptcp@lists.linux.dev, Menglong Dong <imagedong@tencent.com>
Subject: Re: [PATCH mptcp-next v10 0/6] mptcp: add statistics for mptcp socket in use
Date: Mon, 19 Dec 2022 13:44:43 +0100 [thread overview]
Message-ID: <eba99592fd3a550d54ffc7b59df5f4680d575bf8.camel@redhat.com> (raw)
In-Reply-To: <20221219102316.627491-1-imagedong@tencent.com>
On Mon, 2022-12-19 at 18:23 +0800, menglong8.dong@gmail.com wrote:
> From: Menglong Dong <imagedong@tencent.com>
>
> In the 1th patch, we do some code cleanup with replease 'sock->sk'
> with 'sk'. In the 2th patch, we rename 'sk' to 'ssk' in
> mptcp_token_new_connect(). In the 3th patch, we add statistics for mptcp
> socket in use. In the 4th patch, we init the 'sk_prot' field with
> tcp_prot in build_msk. In the 5th patch, we make mptcp_connect can exit
> when receive 'SIGUSR1' with '-r' flag. And in the 6th patch, we add the
> testing for this commit.
>
> With the commit e8695e504942("mptcp: don't orphan ssk in mptcp_close()"),
> I belive that the testing of diag.sh can pass now. In fallback and
> simultaneous close case, the msk can't release normal (sometimes?) without
> that commit, and makes the testing fail. Enn...let's just see that the
> CI is saying~
>
> Changes since v9:
> - rename 'sk' to 'ssk' in the document of mptcp_token_new_connect()
>
> Changes since v8:
> - fix the panic caused by mptcp token KUNIT tests by init sk->sk_prot in
> build_msk()
> - check the state of msk instead of ssk for listening socket
>
> Changes since v7:
> - remove the MPTCP_INUSE flag and do the statistics according to the
> creation and destruction of the token in the 2th patch.
>
> Changes since v6:
> - check all processes exit in flush_pids() in the 4th patch
>
> Changes since v5:
> - introduce MPTCP_INUSE flag to store if msk is in use, as I find
> that it's not correct to check is a msk is in use by
> !sk_unhashed(sk) in mptcp_destroy_common(), because the token
> can be release in mptcp_check_fastclose()
> - add the 3th patch
> - reuse __chk_nr in 4th patch
>
> Changes since v4:
> - rebase to solve merge conflict
>
> Changes since v3:
> - rename MPTCP_DESTROIED to MPTCP_DESTROYED in the 2th patch
>
> Changes since v2:
> - add testing
>
> Changes since v1:
> - split the code cleanup into the 1th patch.
> - decrease the statistics for listening mptcp socket inuse with
> mptcp_listen_inuse_dec()
> - add MPTCP_DESTROIED flags to store if mptcp_destroy_common() was
> called on the msk. For fallback case, we need to decrease the
> statistics only once, and mptcp_destroy_common() can be called
> more than once.
>
> Menglong Dong (6):
> mptcp: introduce 'sk' to replace 'sock->sk' in mptcp_listen()
> mptcp: init sk->sk_prot in build_msk()
> mptcp: rename 'sk' to 'ssk' in mptcp_token_new_connect()
> mptcp: add statistics for mptcp socket in use
> selftest: mptcp: exit from copyfd_io_poll() when receive SIGUSR1
> selftest: mptcp: add test for mptcp socket in use
>
> net/mptcp/protocol.c | 25 ++++++---
> net/mptcp/protocol.h | 2 +-
> net/mptcp/token.c | 14 +++--
> net/mptcp/token_test.c | 3 +
> tools/testing/selftests/net/mptcp/diag.sh | 56 +++++++++++++++++--
> .../selftests/net/mptcp/mptcp_connect.c | 4 +-
> 6 files changed, 85 insertions(+), 19 deletions(-)
>
LGTM, thanks for all the hard work!
Acked-by: Paolo Abeni <pabeni@redhat.com>
next prev parent reply other threads:[~2022-12-19 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 10:23 [PATCH mptcp-next v10 0/6] mptcp: add statistics for mptcp socket in use menglong8.dong
2022-12-19 10:23 ` [PATCH mptcp-next v10 1/6] mptcp: introduce 'sk' to replace 'sock->sk' in mptcp_listen() menglong8.dong
2022-12-19 10:23 ` [PATCH mptcp-next v10 2/6] mptcp: init sk->sk_prot in build_msk() menglong8.dong
2022-12-19 10:23 ` [PATCH mptcp-next v10 3/6] mptcp: rename 'sk' to 'ssk' in mptcp_token_new_connect() menglong8.dong
2022-12-19 10:23 ` [PATCH mptcp-next v10 4/6] mptcp: add statistics for mptcp socket in use menglong8.dong
2022-12-19 10:23 ` [PATCH mptcp-next v10 5/6] selftest: mptcp: exit from copyfd_io_poll() when receive SIGUSR1 menglong8.dong
2022-12-19 10:23 ` [PATCH mptcp-next v10 6/6] selftest: mptcp: add test for mptcp socket in use menglong8.dong
2022-12-19 12:01 ` selftest: mptcp: add test for mptcp socket in use: Tests Results MPTCP CI
2022-12-19 13:50 ` MPTCP CI
2022-12-19 12:44 ` Paolo Abeni [this message]
2022-12-20 12:13 ` [PATCH mptcp-next v10 0/6] mptcp: add statistics for mptcp socket in use Matthieu Baerts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eba99592fd3a550d54ffc7b59df5f4680d575bf8.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=imagedong@tencent.com \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=menglong8.dong@gmail.com \
--cc=mptcp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox