Netdev List
 help / color / mirror / Atom feed
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, donald.hunter@gmail.com,
	petrm@nvidia.com, razor@blackwall.org, daniel@iogearbox.net
Subject: Re: [PATCH net-next 1/2] neighbor: Add NTF_EXT_VALIDATED flag for externally validated entries
Date: Sat, 14 Jun 2025 18:13:13 +0100	[thread overview]
Message-ID: <20250614171313.GB861417@horms.kernel.org> (raw)
In-Reply-To: <20250611141551.462569-2-idosch@nvidia.com>

On Wed, Jun 11, 2025 at 05:15:50PM +0300, Ido Schimmel wrote:

...

> diff --git a/include/uapi/linux/neighbour.h b/include/uapi/linux/neighbour.h
> index b851c36ad25d..27bedfcce537 100644
> --- a/include/uapi/linux/neighbour.h
> +++ b/include/uapi/linux/neighbour.h
> @@ -54,6 +54,7 @@ enum {
>  /* Extended flags under NDA_FLAGS_EXT: */
>  #define NTF_EXT_MANAGED		(1 << 0)
>  #define NTF_EXT_LOCKED		(1 << 1)
> +#define NTF_EXT_EXT_VALIDATED	(1 << 2)
>  
>  /*
>   *	Neighbor Cache Entry States.
> @@ -92,6 +93,10 @@ enum {
>   * bridge in response to a host trying to communicate via a locked bridge port
>   * with MAB enabled. Their purpose is to notify user space that a host requires
>   * authentication.
> + *
> + * NTF_EXT_EXT_VALIDATED flagged neigbor entries were externally validated by a

nit: neighbor or neighbour

> + * user space control plane. The kernel will not remove or invalidate them, but
> + * it can probe them and notify user space when they become reachable.
>   */
>  
>  struct nda_cacheinfo {

...

  parent reply	other threads:[~2025-06-14 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 14:15 [PATCH net-next 0/2] Add support for externally validated neighbor entries Ido Schimmel
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 [this message]
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=20250614171313.GB861417@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --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 \
    --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