From: Ido Schimmel <idosch@nvidia.com>
To: <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
<edumazet@google.com>, <horms@kernel.org>,
<donald.hunter@gmail.com>, <petrm@nvidia.com>,
<razor@blackwall.org>, <daniel@iogearbox.net>,
"Ido Schimmel" <idosch@nvidia.com>
Subject: [PATCH net-next 0/2] Add support for externally validated neighbor entries
Date: Wed, 11 Jun 2025 17:15:49 +0300 [thread overview]
Message-ID: <20250611141551.462569-1-idosch@nvidia.com> (raw)
Patch #1 adds a new neighbor flag ("extern_valid") that prevents the
kernel from invalidating or removing a neighbor entry, while allowing
the kernel to notify user space when the entry becomes reachable. See
motivation and implementation details in the commit message.
Patch #2 adds a selftest.
Ido Schimmel (2):
neighbor: Add NTF_EXT_VALIDATED flag for externally validated entries
selftests: net: Add a selftest for externally validated neighbor
entries
Documentation/netlink/specs/rt-neigh.yaml | 1 +
include/net/neighbour.h | 4 +-
include/uapi/linux/neighbour.h | 5 +
net/core/neighbour.c | 75 ++++-
tools/testing/selftests/net/Makefile | 1 +
tools/testing/selftests/net/test_neigh.sh | 337 ++++++++++++++++++++++
6 files changed, 413 insertions(+), 10 deletions(-)
create mode 100755 tools/testing/selftests/net/test_neigh.sh
--
2.49.0
next reply other threads:[~2025-06-11 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 14:15 Ido Schimmel [this message]
2025-06-11 14:15 ` [PATCH net-next 1/2] neighbor: Add NTF_EXT_VALIDATED flag for externally validated entries Ido Schimmel
2025-06-12 10:26 ` Nikolay Aleksandrov
2025-06-13 8:23 ` Daniel Borkmann
2025-06-17 14:09 ` Ido Schimmel
2025-06-17 14:21 ` Daniel Borkmann
2025-06-14 17:13 ` Simon Horman
2025-06-11 14:15 ` [PATCH net-next 2/2] selftests: net: Add a selftest for externally validated neighbor entries Ido Schimmel
2025-06-12 10:26 ` Nikolay Aleksandrov
2025-06-14 17:11 ` Simon Horman
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=20250611141551.462569-1-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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