From: Ido Schimmel <idosch@nvidia.com>
To: Sascha Frey <sf@techfak.net>
Cc: netdev@vger.kernel.org, qotmddnjs@ajou.ac.kr,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com
Subject: Re: [REGRESSION] vxlan: duplicate ICMP replies with nexthop FDB entries after 3fa64d86fc64
Date: Wed, 28 Oct 2026 17:08:24 +0200 [thread overview]
Message-ID: <20261028150824.GA992905@shredder> (raw)
In-Reply-To: <20261028142928.GA8406@techfak.de>
On Wed, Oct 28, 2026 at 03:29:28PM +0100, Sascha Frey wrote:
> Could someone help investigate whether the new checks can interfere with
> EVPN/FRR-installed nexthop FDB entries, or whether this exposes another
> issue in the VXLAN FDB handling?
I believe we need to relax the checks to allow "extern_learn" entries.
They are not subject to ageing (vxlan_cleanup() skips them), so they
cannot trigger the bug that commit 98fc57d16744 ("vxlan: reject dynamic
fdb entries that reference a nexthop id") fixed. Let me do some testing.
next prev parent reply other threads:[~2026-10-28 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 14:29 [REGRESSION] vxlan: duplicate ICMP replies with nexthop FDB entries after 3fa64d86fc64 Sascha Frey
2026-10-28 15:08 ` Ido Schimmel [this message]
2026-10-28 17:57 ` Ido Schimmel
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=20261028150824.GA992905@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qotmddnjs@ajou.ac.kr \
--cc=sf@techfak.net \
/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