mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bastien Curutchet (eBPF Foundation)" <bastien.curutchet@bootlin.com>
To: Alexei Starovoitov <ast@kernel.org>,
	 Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	 Martin KaFai Lau <martin.lau@linux.dev>,
	 Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	 Yonghong Song <yonghong.song@linux.dev>,
	 John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	 Stanislav Fomichev <sdf@fomichev.me>,
	Hao Luo <haoluo@google.com>,  Jiri Olsa <jolsa@kernel.org>,
	Mykola Lysenko <mykolal@fb.com>,  Shuah Khan <shuah@kernel.org>
Cc: Alexis Lothore <alexis.lothore@bootlin.com>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
	 linux-kselftest@vger.kernel.org,
	 "Bastien Curutchet (eBPF Foundation)"
	<bastien.curutchet@bootlin.com>
Subject: [PATCH bpf-next 1/2] selftests/bpf: lwt_seg6local: Remove unused routes
Date: Fri, 07 Mar 2025 10:18:23 +0100	[thread overview]
Message-ID: <20250307-seg6local-v1-1-990fff8f180d@bootlin.com> (raw)
In-Reply-To: <20250307-seg6local-v1-0-990fff8f180d@bootlin.com>

Some routes in fb00:: are initialized during setup, even though they
aren't needed by the test as the UDP packets will travel through the
lightweight tunnels.

Remove these unnecessary routes.

Signed-off-by: Bastien Curutchet (eBPF Foundation) <bastien.curutchet@bootlin.com>
---
 tools/testing/selftests/bpf/test_lwt_seg6local.sh | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/tools/testing/selftests/bpf/test_lwt_seg6local.sh b/tools/testing/selftests/bpf/test_lwt_seg6local.sh
index 0efea2292d6aac3a33f4745b1cdbda803fd1f307..9c74b88730ffd98f8e988a078d218ffbcd9ee95c 100755
--- a/tools/testing/selftests/bpf/test_lwt_seg6local.sh
+++ b/tools/testing/selftests/bpf/test_lwt_seg6local.sh
@@ -99,19 +99,14 @@ ip netns exec ${NS6} ip link set dev lo up
 
 # All link scope addresses and routes required between veths
 ip netns exec ${NS1} ip -6 addr add fb00::12/16 dev veth1 scope link
-ip netns exec ${NS1} ip -6 route add fb00::21 dev veth1 scope link
 ip netns exec ${NS2} ip -6 addr add fb00::21/16 dev veth2 scope link
 ip netns exec ${NS2} ip -6 addr add fb00::34/16 dev veth3 scope link
-ip netns exec ${NS2} ip -6 route add fb00::43 dev veth3 scope link
-ip netns exec ${NS3} ip -6 route add fb00::65 dev veth5 scope link
 ip netns exec ${NS3} ip -6 addr add fb00::43/16 dev veth4 scope link
 ip netns exec ${NS3} ip -6 addr add fb00::56/16 dev veth5 scope link
 ip netns exec ${NS4} ip -6 addr add fb00::65/16 dev veth6 scope link
 ip netns exec ${NS4} ip -6 addr add fb00::78/16 dev veth7 scope link
-ip netns exec ${NS4} ip -6 route add fb00::87 dev veth7 scope link
 ip netns exec ${NS5} ip -6 addr add fb00::87/16 dev veth8 scope link
 ip netns exec ${NS5} ip -6 addr add fb00::910/16 dev veth9 scope link
-ip netns exec ${NS5} ip -6 route add fb00::109 dev veth9 scope link
 ip netns exec ${NS5} ip -6 route add fb00::109 table 117 dev veth9 scope link
 ip netns exec ${NS6} ip -6 addr add fb00::109/16 dev veth10 scope link
 

-- 
2.48.1


  reply	other threads:[~2025-03-07  9:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07  9:18 [PATCH bpf-next 0/2] selftests/bpf: Move test_lwt_seg6local to test_progs Bastien Curutchet (eBPF Foundation)
2025-03-07  9:18 ` Bastien Curutchet (eBPF Foundation) [this message]
2025-03-07  9:18 ` [PATCH bpf-next 2/2] selftests/bpf: lwt_seg6local: Move test " Bastien Curutchet (eBPF Foundation)
2025-03-08  4:54 ` [PATCH bpf-next 0/2] selftests/bpf: Move test_lwt_seg6local " Stanislav Fomichev
2025-03-08  9:30 ` 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=20250307-seg6local-v1-1-990fff8f180d@bootlin.com \
    --to=bastien.curutchet@bootlin.com \
    --cc=alexis.lothore@bootlin.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yonghong.song@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

all inboxes | Powered by JetHome®