[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241112142234.7abf2232@kernel.org>
Date: Tue, 12 Nov 2024 14:22:34 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Petr Machata <petrm@...dia.com>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
<netdev@...r.kernel.org>, Simon Horman <horms@...nel.org>, Ido Schimmel
<idosch@...dia.com>, Amit Cohen <amcohen@...dia.com>, Vladimir Oltean
<vladimir.oltean@....com>, Andy Roulin <aroulin@...dia.com>,
<mlxsw@...dia.com>, Shuah Khan <skhan@...uxfoundation.org>, Shuah Khan
<shuah@...nel.org>, Benjamin Poirier <bpoirier@...dia.com>, Hangbin Liu
<liuhangbin@...il.com>, <linux-kselftest@...r.kernel.org>, Jiri Pirko
<jiri@...nulli.us>
Subject: Re: [PATCH net-next v3 7/7] selftests: net: fdb_notify: Add a test
for FDB notifications
On Mon, 11 Nov 2024 18:09:01 +0100 Petr Machata wrote:
> Check that only one notification is produced for various FDB edit
> operations.
>
> Regarding the ip_link_add() and ip_link_master() helpers. This pattern of
> action plus corresponding defer is bound to come up often, and a dedicated
> vocabulary to capture it will be handy. tunnel_create() and vlan_create()
> from forwarding/lib.sh are somewhat opaque and perhaps too kitchen-sinky,
> so I tried to go in the opposite direction with these ones, and wrapped
> only the bare minimum to schedule a corresponding cleanup.
Looks like it fails about half of the time :(
https://netdev.bots.linux.dev/flakes.html?min-flip=0&tn-needle=fdb-notify&br-cnt=200
--
pw-bot: cr
Powered by blists - more mailing lists