From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v3 1/2] Squash to "selftests/bpf: Add mptcp subflow subtest"
Date: Thu, 16 May 2024 16:38:56 +0800 [thread overview]
Message-ID: <e301d8027ec2ed1a9e77f461680593f30c5e2ced.1715848543.git.tanggeliang@kylinos.cn> (raw)
In-Reply-To: <cover.1715848543.git.tanggeliang@kylinos.cn>
From: Geliang Tang <tanggeliang@kylinos.cn>
create_netns() is updated in "bpf-next add netns helpers" series,
test_subflow() needs to be updated too.
That means v3 of "selftests/bpf: new MPTCP subflow subtest" cannot be sent
to bpf-next at the moment until this "bpf-next add netns helpers" series is
accepted.
Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
---
tools/testing/selftests/bpf/prog_tests/mptcp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/prog_tests/mptcp.c b/tools/testing/selftests/bpf/prog_tests/mptcp.c
index c7f61fd9e7a5..a4863328d2c7 100644
--- a/tools/testing/selftests/bpf/prog_tests/mptcp.c
+++ b/tools/testing/selftests/bpf/prog_tests/mptcp.c
@@ -418,7 +418,7 @@ static void test_subflow(void)
if (!ASSERT_OK(err, "prog_attach"))
goto skel_destroy;
- nstoken = create_netns();
+ nstoken = create_netns(NS_TEST);
if (!ASSERT_OK_PTR(nstoken, "create_netns: mptcp_subflow"))
goto skel_destroy;
--
2.43.0
next prev parent reply other threads:[~2024-05-16 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 8:38 [PATCH mptcp-next v3 0/2] fixes for create_netns Geliang Tang
2024-05-16 8:38 ` Geliang Tang [this message]
2024-05-16 8:38 ` [PATCH mptcp-next v3 2/2] Squash to "selftests/bpf: Add bpf scheduler test" Geliang Tang
2024-05-16 9:31 ` [PATCH mptcp-next v3 0/2] fixes for create_netns MPTCP CI
2024-05-30 6:53 ` Geliang Tang
2024-05-30 9:06 ` 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=e301d8027ec2ed1a9e77f461680593f30c5e2ced.1715848543.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).