[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <efcc6e11-2d3a-489e-80bc-cbc3f72f7afa@hetzner-cloud.de>
Date: Tue, 25 Feb 2025 16:07:27 +0100
From: Marcus Wichelmann <marcus.wichelmann@...zner-cloud.de>
To: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org, linux-kselftest@...r.kernel.org
Cc: willemdebruijn.kernel@...il.com, jasowang@...hat.com,
andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, andrii@...nel.org, eddyz87@...il.com,
mykolal@...com, ast@...nel.org, daniel@...earbox.net, martin.lau@...ux.dev,
song@...nel.org, yonghong.song@...ux.dev, john.fastabend@...il.com,
kpsingh@...nel.org, sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org,
shuah@...nel.org, hawk@...nel.org
Subject: Re: [PATCH bpf-next v3 4/6] selftests/bpf: refactor
xdp_context_functional test and bpf program
Am 24.02.25 um 16:29 schrieb Marcus Wichelmann:
> [...]
> + /* By default, Linux sends IPv6 multicast listener reports which
> + * interfere with this test. Set the IFF_NOARP flag to ensure
> + * silence on the interface.
> + */
> + SYS(close, "ip link set dev " RX_NAME " arp off");
> SYS(close, "ip link set dev " RX_NAME " up");
Hm, setting the NOARP flag seems to have not been sufficient to fix the flaky
test:
https://github.com/kernel-patches/bpf/actions/runs/13507111620/job/37739614229
I was not able to reproduce it locally or with my own CI runs unfortunately, but
I'll try something else in the next patch version which should definitely stop
IPv6 multicast listener report packets from messing with the tests.
Powered by blists - more mailing lists