From: Zhefu Peng <ilskdw@gmail.com>
To: nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, kuniyu@google.com,
mschiffer@universe-factory.net
Subject: Re: [PATCH net v3] vxlan: reset the remote's dst cache when snooping moves a MAC
Date: Fri, 13 Nov 2026 23:51:10 +0800 [thread overview]
Message-ID: <20261113155110.75061-1-ilskdw@gmail.com> (raw)
In-Reply-To: <72d0afdb-c2c6-458f-9363-d16c32220a6a@6wind.com>
On 13/11/2026 16:05, Nicolas Dichtel wrote:
> Maybe a selftest could be added to check this scenario?
Sure. v4 will add one under tools/testing/selftests/net that covers
both cases: the IPv4 move behind a router and the IPv6 link-local move.
pw-bot: cr
prev parent reply other threads:[~2026-11-13 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 18:00 [PATCH net v3] vxlan: reset the remote's dst cache when snooping moves a MAC Zhefu Peng
2026-11-13 15:05 ` Nicolas Dichtel
2026-11-13 15:51 ` Zhefu Peng [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=20261113155110.75061-1-ilskdw@gmail.com \
--to=ilskdw@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=mschiffer@universe-factory.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.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