From: Simon Horman <horms@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Mat Martineau <martineau@kernel.org>,
Geliang Tang <geliang@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Shuah Khan <shuah@kernel.org>,
mptcp@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 2/2] selftests: mptcp: explicitly trigger the listener diag code-path
Date: Mon, 26 Feb 2024 17:40:31 +0000 [thread overview]
Message-ID: <20240226174031.GH13129@kernel.org> (raw)
In-Reply-To: <22424f1c-3f76-454d-9de4-486c3f2f2478@kernel.org>
On Thu, Feb 22, 2024 at 03:49:44PM +0100, Matthieu Baerts wrote:
> Hi Simon,
>
> Thank you for the review!
>
> On 22/02/2024 2:13 pm, Simon Horman wrote:
> > On Wed, Feb 22, 2024 at 12:46:59PM +0100, Paolo Abeni wrote:
> >> l The mptcp diag interface already experienced a few locking bugs
> >> that lockdep and appropriate coverage have detected in advance.
> >>
> >> Let's add a test-case triggering the relevant code path, to prevent
> >> similar issues in the future.
> >>
> >> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> >> ---
> >> tools/testing/selftests/net/mptcp/diag.sh | 30 +++++++++++++++++++++++
> >> 1 file changed, 30 insertions(+)
> >>
> >> diff --git a/tools/testing/selftests/net/mptcp/diag.sh b/tools/testing/selftests/net/mptcp/diag.sh
> >> index 60a7009ce1b5..3ab584b38566 100755
> >> --- a/tools/testing/selftests/net/mptcp/diag.sh
> >> +++ b/tools/testing/selftests/net/mptcp/diag.sh
> >> @@ -81,6 +81,21 @@ chk_msk_nr()
> >> __chk_msk_nr "grep -c token:" "$@"
> >> }
> >>
> >> +chk_listener_nr()
> >> +{
> >> + local expected=$1
> >> + local msg="$2"
> >> +
> >> + if [ $expected -gt 0 ] && \
> >> + ! mptcp_lib_kallsyms_has "mptcp_diag_dump_listeners"; then
> >> + printf "%-50s%s\n" "$msg - mptcp" "[ skip ]"
> >> + mptcp_lib_result_skip "many listener sockets"
> >> + else
> >> + __chk_nr "ss -inmlHMON $ns | wc -l" "$expected" "$msg - mptcp"
> >> + fi
> >> + __chk_nr "ss -inmlHtON $ns | wc -l" "$expected" "$msg - subflows"
> >> +}
> >> +
> >> wait_msk_nr()
> >> {
> >> local condition="grep -c token:"
> >> @@ -279,5 +294,20 @@ flush_pids
> >> chk_msk_inuse 0 "many->0"
> >> chk_msk_cestab 0 "many->0"
> >>
> >> +chk_listener_nr 0 "no listener sockets"
> >> +NR_SERVERS=100
> >> +for I in $(seq 1 $NR_SERVERS); do
> >> + ip netns exec $ns ./mptcp_connect -p $((I + 20001)) -l 0.0.0.0 2>&1 >/dev/null &
> >> + mptcp_lib_wait_local_port_listen $ns $((I + 20001))
> >> +done
> >> +
> >> +chk_listener_nr $NR_SERVERS "many listener sockets"
> >> +
> >> +# gracefull termination
> >
> > nit, as you plan to re-spin anyway: graceful
>
> Paolo sent a new version on MPTCP ML only. When applying the new
> version, I fixed this:
>
> https://lore.kernel.org/mptcp/e98b8b07-558c-498a-97fb-dd5cab11e439@kernel.org/
>
> >> +for I in $(seq 1 $NR_SERVERS); do
> >> + echo a | ip netns exec $ns ./mptcp_connect -p $((I + 20001)) 127.0.0.1 2>&1 >/dev/null
> >
> > I'm not sure of the validity of this but shellcheck complains that:
> >
> > SC2069 (warning): To redirect stdout+stderr, 2>&1 must be last (or use '{ cmd > file; } 2>&1' to clarify).
> >
> > Also for the same constriction slightly earlier in this patch.
>
> Good catch!
>
> I should add shellcheck support in our CI to catch that :)
>
> I just applied the suggested modification in our tree [1]. The new
> version that will be sent to netdev will no longer have this issue.
>
> https://github.com/multipath-tcp/mptcp_net-next/commit/31f1460d552c
Thanks Matt,
much appreciated.
prev parent reply other threads:[~2024-02-26 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 11:46 [PATCH net 0/2] mptcp: fix another deadlock issue Paolo Abeni
2024-02-21 11:46 ` [PATCH net 1/2] mptcp: fix possible deadlock in subflow diag Paolo Abeni
2024-02-21 11:46 ` [PATCH net 2/2] selftests: mptcp: explicitly trigger the listener diag code-path Paolo Abeni
2024-02-21 15:19 ` Paolo Abeni
2024-02-22 13:13 ` Simon Horman
2024-02-22 14:49 ` Matthieu Baerts
2024-02-26 17:40 ` Simon Horman [this message]
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=20240226174031.GH13129@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).