From: Simon Horman <horms@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, petrm@nvidia.com
Subject: Re: [PATCH net-next] selftests: forwarding: Make vxlan-bridge-1d pass on debug kernels
Date: Mon, 8 Jul 2024 11:30:54 +0100 [thread overview]
Message-ID: <20240708103054.GK1481495@kernel.org> (raw)
In-Reply-To: <20240707095458.2870260-1-idosch@nvidia.com>
On Sun, Jul 07, 2024 at 12:54:58PM +0300, Ido Schimmel wrote:
> The ageing time used by the test is too short for debug kernels and
> results in entries being aged out prematurely [1].
>
> Fix by increasing the ageing time.
>
> The same change was done for the VLAN-aware version of the test in
> commit dfbab74044be ("selftests: forwarding: Make vxlan-bridge-1q pass
> on debug kernels").
>
> [1]
> # ./vxlan_bridge_1d.sh
> [...]
> # TEST: VXLAN: flood before learning [ OK ]
> # TEST: VXLAN: show learned FDB entry [ OK ]
> # TEST: VXLAN: learned FDB entry [FAIL]
> # veth3: Expected to capture 0 packets, got 4.
> # RTNETLINK answers: No such file or directory
> # TEST: VXLAN: deletion of learned FDB entry [ OK ]
> # TEST: VXLAN: Ageing of learned FDB entry [FAIL]
> # veth3: Expected to capture 0 packets, got 2.
> [...]
>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> Reviewed-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-07-08 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 9:54 [PATCH net-next] selftests: forwarding: Make vxlan-bridge-1d pass on debug kernels Ido Schimmel
2024-07-08 10:30 ` Simon Horman [this message]
2024-07-09 18:20 ` 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=20240708103054.GK1481495@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
/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).