From: Ido Schimmel <idosch@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, razor@blackwall.org
Subject: Re: [PATCH net] selftests: test_bridge_neigh_suppress.sh: Try to stabilize test
Date: Tue, 7 May 2024 13:58:07 +0300 [thread overview]
Message-ID: <ZjoJPxVOThaGKTZO@shredder> (raw)
In-Reply-To: <20240506063613.15568681@kernel.org>
On Mon, May 06, 2024 at 06:36:13AM -0700, Jakub Kicinski wrote:
> On Sun, 5 May 2024 17:54:12 +0300 Ido Schimmel wrote:
> > I'm unable to reproduce these failures locally.
>
> :(
tl;dr - I was able to reproduce the issue (hopefully the same one as in
the CI) and will post a fix soon.
I woke in the middle of the night and for some reason it occurred to me
that the problem might be related to the MACAddressPolicy=persistent
nonsense that systemd made the default since version 242 [1].
The test creates the veth pairs in the initial network namespace before
moving them to one of the namespaces created by the test. Since they are
created in the same namespace and with the same name, udev will assign
them the same MAC address which breaks bridging.
The reason I couldn't initially reproduce the issue is that long ago I
added the following snippet [2] to the kickstart file with which we
install Fedora on our machines.
[1] https://lore.kernel.org/netdev/20200416095314.0a1dff38@strong.id.au/
[2]
# Prevent systemd from changing MAC addresses
%post
cat > /etc/systemd/network/10-ignore.link << EOL
[Match]
OriginalName=*
[Link]
MACAddressPolicy=none
EOL
%end
prev parent reply other threads:[~2024-05-07 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 14:54 [PATCH net] selftests: test_bridge_neigh_suppress.sh: Try to stabilize test Ido Schimmel
2024-05-06 8:08 ` Ido Schimmel
2024-05-06 13:36 ` Jakub Kicinski
2024-05-07 10:58 ` Ido Schimmel [this message]
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=ZjoJPxVOThaGKTZO@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
/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).