The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: James Raphael Tiovalen <jamestiotio@gmail.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org,  stable@vger.kernel.org,
	Kees Cook <kees@kernel.org>,
	 Nikolay Aleksandrov <razor@blackwall.org>,
	Ido Schimmel <idosch@nvidia.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] vxlan: mdb: Fix source list corruption on a failed replace
Date: Wed, 22 Jul 2026 10:25:03 +0200	[thread overview]
Message-ID: <amB-O8v0P2AfY9Oh@kwain> (raw)
In-Reply-To: <20260720160428.249356-1-jamestiotio@gmail.com>

On Tue, Jul 21, 2026 at 12:04:24AM +0800, James Raphael Tiovalen wrote:
> When replacing the source list of an MDB remote entry, all existing
> sources are first marked for deletion and vxlan_mdb_remote_srcs_add()
> is then called to add the new source list. Sources present in the new
> list have their deletion mark cleared, and any sources left marked
> afterwards are removed.
> 
> If vxlan_mdb_remote_srcs_add() fails partway through, its error path
> deletes all entries on the remote's source list. That rollback is only
> correct for its other caller, vxlan_mdb_remote_add(), where the remote
> was just allocated and the list contains solely entries added during
> the call. On the replace path the list also holds pre-existing sources,
> so a failed replace tears them down together with their (S, G)
> forwarding entries instead of leaving the entry unchanged.
> 
> This is reachable from an existing (*, G) remote. An EXCLUDE filter
> that loses sources starts forwarding traffic that should be blocked,
> while an INCLUDE filter that loses sources drops traffic that should be
> forwarded.
> 
> Mark entries created during the current pass with a new
> VXLAN_SGRP_F_NEW flag. On failure, delete only those entries and clear
> the deletion mark on the pre-existing ones, so a failed replace leaves
> the source list untouched. Retain the flag until the whole operation
> succeeds and then clear it. Also stop vxlan_mdb_remote_src_add() from
> deleting a pre-existing entry it only looked up when adding that
> entry's forwarding entry fails.
> 
> Fixes: a3a48de5eade ("vxlan: mdb: Add MDB control path support")
> Cc: stable@vger.kernel.org
> Signed-off-by: James Raphael Tiovalen <jamestiotio@gmail.com>

Reviewed-by: Antoine Tenart <atenart@kernel.org>

> ---
>  drivers/net/vxlan/vxlan_mdb.c | 30 ++++++++++++++++++------------
>  1 file changed, 18 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/net/vxlan/vxlan_mdb.c b/drivers/net/vxlan/vxlan_mdb.c
> index 055a4969f593..af7a0d7f95a5 100644
> --- a/drivers/net/vxlan/vxlan_mdb.c
> +++ b/drivers/net/vxlan/vxlan_mdb.c
> @@ -42,6 +42,7 @@ struct vxlan_mdb_remote {
>  };
>  
>  #define VXLAN_SGRP_F_DELETE	BIT(0)
> +#define VXLAN_SGRP_F_NEW	BIT(1)
>  
>  struct vxlan_mdb_src_entry {
>  	struct hlist_node node;
> @@ -844,6 +845,7 @@ vxlan_mdb_remote_src_add(const struct vxlan_mdb_config *cfg,
>  		ent = vxlan_mdb_remote_src_entry_add(remote, &src->addr);
>  		if (!ent)
>  			return -ENOMEM;
> +		ent->flags |= VXLAN_SGRP_F_NEW;
>  	} else if (!(cfg->nlflags & NLM_F_REPLACE)) {
>  		NL_SET_ERR_MSG_MOD(extack, "Source entry already exists");
>  		return -EEXIST;
> @@ -853,15 +855,16 @@ vxlan_mdb_remote_src_add(const struct vxlan_mdb_config *cfg,
>  	if (err)
>  		goto err_src_del;
>  
> -	/* Clear flags in case source entry was marked for deletion as part of
> -	 * replace flow.
> +	/* Clear the deletion mark so the entry survives the replace sweep.
> +	 * The new mark is retained until the whole operation succeeds.
>  	 */
> -	ent->flags = 0;
> +	ent->flags &= ~VXLAN_SGRP_F_DELETE;
>  
>  	return 0;
>  
>  err_src_del:
> -	vxlan_mdb_remote_src_entry_del(ent);
> +	if (ent->flags & VXLAN_SGRP_F_NEW)
> +		vxlan_mdb_remote_src_entry_del(ent);
>  	return err;
>  }
>  
> @@ -889,11 +892,19 @@ static int vxlan_mdb_remote_srcs_add(const struct vxlan_mdb_config *cfg,
>  			goto err_src_del;
>  	}
>  
> +	hlist_for_each_entry(ent, &remote->src_list, node)
> +		ent->flags &= ~VXLAN_SGRP_F_NEW;
> +
>  	return 0;
>  
>  err_src_del:
> -	hlist_for_each_entry_safe(ent, tmp, &remote->src_list, node)
> -		vxlan_mdb_remote_src_del(cfg->vxlan, &cfg->group, remote, ent);
> +	hlist_for_each_entry_safe(ent, tmp, &remote->src_list, node) {
> +		if (ent->flags & VXLAN_SGRP_F_NEW)
> +			vxlan_mdb_remote_src_del(cfg->vxlan, &cfg->group, remote,
> +						 ent);
> +		else
> +			ent->flags &= ~VXLAN_SGRP_F_DELETE;
> +	}
>  	return err;
>  }
>  
> @@ -1069,7 +1080,7 @@ vxlan_mdb_remote_srcs_replace(const struct vxlan_mdb_config *cfg,
>  
>  	err = vxlan_mdb_remote_srcs_add(cfg, remote, extack);
>  	if (err)
> -		goto err_clear_delete;
> +		return err;
>  
>  	hlist_for_each_entry_safe(ent, tmp, &remote->src_list, node) {
>  		if (ent->flags & VXLAN_SGRP_F_DELETE)
> @@ -1078,11 +1089,6 @@ vxlan_mdb_remote_srcs_replace(const struct vxlan_mdb_config *cfg,
>  	}
>  
>  	return 0;
> -
> -err_clear_delete:
> -	hlist_for_each_entry(ent, &remote->src_list, node)
> -		ent->flags &= ~VXLAN_SGRP_F_DELETE;
> -	return err;
>  }
>  
>  static int vxlan_mdb_remote_replace(const struct vxlan_mdb_config *cfg,
> -- 
> 2.43.0
> 

  parent reply	other threads:[~2026-07-22  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 16:04 [PATCH net] vxlan: mdb: Fix source list corruption on a failed replace James Raphael Tiovalen
2026-07-22  8:02 ` Ido Schimmel
2026-07-22  8:25 ` Antoine Tenart [this message]
2026-07-22  9:40 ` Nikolay Aleksandrov
2026-07-22 21:00 ` 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=amB-O8v0P2AfY9Oh@kwain \
    --to=atenart@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=jamestiotio@gmail.com \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=stable@vger.kernel.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