From: Guillaume Nault <gnault@redhat.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Vadim Fedorenko <vfedorenko@novek.ru>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 0/2] selftests: pmtu.sh: Fix cleanup of processes launched in subshell.
Date: Wed, 9 Mar 2022 01:55:06 +0100 [thread overview]
Message-ID: <20220309005506.GA1708@debian.home> (raw)
In-Reply-To: <36d7619f-0fb4-e23b-2d2b-e0d27fd517ee@linuxfoundation.org>
On Tue, Mar 08, 2022 at 04:51:46PM -0700, Shuah Khan wrote:
> On 3/8/22 3:14 PM, Guillaume Nault wrote:
> > Depending on the options used, pmtu.sh may launch tcpdump and nettest
> > processes in the background. However it fails to clean them up after
> > the tests complete.
> >
> > Patch 1 allows the cleanup() function to read the list of PIDs launched
> > by the tests.
> > Patch 2 fixes the way the nettest PIDs are retrieved.
> >
> > v2:
> > * Use tcpdump's immediate mode to capture packets even in short lived
> > tests.
> > * Add patch 2 to fix the nettest_pids list.
> >
> > Guillaume Nault (2):
> > selftests: pmtu.sh: Kill tcpdump processes launched by subshell.
> > selftests: pmtu.sh: Kill nettest processes launched in subshell.
> >
> > tools/testing/selftests/net/pmtu.sh | 21 +++++++++++++++++----
> > 1 file changed, 17 insertions(+), 4 deletions(-)
> >
>
> Both of these look good to me. One nit on commit header. Please
> include net in the patch subject line in the future.
>
> e.g: selftests:net pmtu.sh
Thanks, I'll do that next time (I just reused keywords used by other
commits for this file).
> Tested them on my system. Seeing these messages even after building
> nettest:
>
> 'nettest' command not found; skipping tests
> xfrm6udp not supported
> TEST: vti6: PMTU exceptions (ESP-in-UDP) [SKIP]
> 'nettest' command not found; skipping tests
> xfrm4udp not supported
> TEST: vti4: PMTU exceptions (ESP-in-UDP) [SKIP]
> 'nettest' command not found; skipping tests
> xfrm6udprouted not supported
> TEST: vti6: PMTU exceptions, routed (ESP-in-UDP) [SKIP]
> 'nettest' command not found; skipping tests
> xfrm4udprouted not supported
>
> Might not be related to this patch though. I jusr ran pmtu.sh from
> net directory.
Personally I just modified my PATH before running pmtu.sh. Not sure if
there's a better way. But in any case, that's not related to this
patch.
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
>
> thanks,
> -- Shuah
>
next prev parent reply other threads:[~2022-03-09 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 22:14 [PATCH net 0/2] selftests: pmtu.sh: Fix cleanup of processes launched in subshell Guillaume Nault
2022-03-08 22:15 ` [PATCH net 1/2] selftests: pmtu.sh: Kill tcpdump processes launched by subshell Guillaume Nault
2022-03-08 22:15 ` [PATCH net 2/2] selftests: pmtu.sh: Kill nettest processes launched in subshell Guillaume Nault
2022-03-08 23:51 ` [PATCH net 0/2] selftests: pmtu.sh: Fix cleanup of " Shuah Khan
2022-03-09 0:55 ` Guillaume Nault [this message]
2022-03-10 5:00 ` patchwork-bot+netdevbpf
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=20220309005506.GA1708@debian.home \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vfedorenko@novek.ru \
/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).