From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v4 5/7] selftests: mptcp: add mptcp_lib_make_file
Date: Mon, 23 Oct 2023 01:25:48 +0200 [thread overview]
Message-ID: <fca43859-3cda-4d30-97e5-dc36e0ba8ea9@kernel.org> (raw)
In-Reply-To: <985c9a3186e32bb08bd3d617c9a0c7653dda112c.1697182955.git.geliang.tang@suse.com>
Hi Geliang,
On 13/10/2023 09:44, Geliang Tang wrote:
> To avoid duplicated code in different MPTCP selftests, we can add
> and use helpers defined in mptcp_lib.sh.
>
> make_file() helper in mptcp_sockopt.sh and userspace_pm.sh are the same.
> Export it into mptcp_lib.sh and rename it as mptcp_lib_kill_wait(). Use
> it in both mptcp_connect.sh and mptcp_join.sh.
Thank you for the new verison!
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh b/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh
> index bfa744e350ef..755ae0f5ac4b 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_sockopt.sh
> @@ -251,8 +251,7 @@ make_file()
> local who=$2
> local size=$3
>
> - dd if=/dev/urandom of="$name" bs=1024 count=$size 2> /dev/null
> - echo -e "\nMPTCP_TEST_FILE_END_MARKER" >> "$name"
> + mptcp_lib_make_file $name $bs $size
Here, '$bs' is not declared, I guess you should use '1024' instead.
I can fix that when applying the patch if there is nothing else.
Cheers,
Matt
next prev parent reply other threads:[~2023-10-22 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 7:44 [PATCH mptcp-next v4 0/7] export helpers to mptcp_lib.sh Geliang Tang
2023-10-13 7:44 ` [PATCH mptcp-next v4 1/7] selftests: mptcp: add mptcp_lib_kill_wait Geliang Tang
2023-10-13 7:44 ` [PATCH mptcp-next v4 2/7] selftests: mptcp: add mptcp_lib_is_v6 Geliang Tang
2023-10-13 7:44 ` [PATCH mptcp-next v4 3/7] selftests: mptcp: add mptcp_lib_get_counter Geliang Tang
2023-10-13 7:44 ` [PATCH mptcp-next v4 4/7] selftests: mptcp: add missing oflag=append Geliang Tang
2023-10-13 7:44 ` [PATCH mptcp-next v4 5/7] selftests: mptcp: add mptcp_lib_make_file Geliang Tang
2023-10-22 23:25 ` Matthieu Baerts [this message]
2023-10-13 7:44 ` [PATCH mptcp-next v4 6/7] selftests: mptcp: add mptcp_lib_check_transfer Geliang Tang
2023-10-13 7:44 ` [PATCH mptcp-next v4 7/7] selftests: mptcp: add mptcp_lib_wait_local_port_listen Geliang Tang
2023-10-13 9:28 ` selftests: mptcp: add mptcp_lib_wait_local_port_listen: Tests Results MPTCP CI
2023-10-22 23:30 ` [PATCH mptcp-next v4 0/7] export helpers to mptcp_lib.sh Matthieu Baerts
2023-10-22 23:48 ` 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=fca43859-3cda-4d30-97e5-dc36e0ba8ea9@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang.tang@suse.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