public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Maurer <fmaurer@redhat.com>
To: luka.gejak@linux.dev
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org, horms@kernel.org,
	liuhangbin@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/4] net: hsr: fix VLAN add unwind on slave errors
Date: Fri, 27 Mar 2026 12:52:02 +0100	[thread overview]
Message-ID: <acZvYp_SYvypHWgk@thinkpad> (raw)
In-Reply-To: <20260326154715.38405-3-luka.gejak@linux.dev>

Thank you for updating this patch!

On Thu, Mar 26, 2026 at 04:47:13PM +0100, luka.gejak@linux.dev wrote:
> From: Luka Gejak <luka.gejak@linux.dev>
>
> When vlan_vid_add() fails for a secondary slave, the error path calls
> vlan_vid_del() on the failing port instead of the peer slave that had
> already succeeded. This results in asymmetric VLAN state across the HSR
> pair.
>
> Fix this by switching to a centralized unwind path that removes the VID
> from any slave device that was already programmed.
>
> Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
> ---
>  net/hsr/hsr_device.c | 46 ++++++++++++++++++++++++++------------------
>  1 file changed, 27 insertions(+), 19 deletions(-)
>
> diff --git a/net/hsr/hsr_device.c b/net/hsr/hsr_device.c
> index 5c3eca2235ce..75c491279df8 100644
> --- a/net/hsr/hsr_device.c
> +++ b/net/hsr/hsr_device.c
> @@ -532,8 +532,8 @@ static void hsr_change_rx_flags(struct net_device *dev, int change)
>  static int hsr_ndo_vlan_rx_add_vid(struct net_device *dev,
>  				   __be16 proto, u16 vid)
>  {
> -	bool is_slave_a_added = false;
> -	bool is_slave_b_added = false;
> +	struct net_device *slave_a_dev = NULL;
> +	struct net_device *slave_b_dev = NULL;
>  	struct hsr_port *port;
>  	struct hsr_priv *hsr;
>  	int ret = 0;
> @@ -546,29 +546,28 @@ static int hsr_ndo_vlan_rx_add_vid(struct net_device *dev,
>  			continue;
>
>  		ret = vlan_vid_add(port->dev, proto, vid);
> -		switch (port->type) {
> -		case HSR_PT_SLAVE_A:
> -			if (ret) {
> -				/* clean up Slave-B */
> +		if (ret) {
> +			switch (port->type) {
> +			case HSR_PT_SLAVE_A:
>  				netdev_err(dev, "add vid failed for Slave-A\n");
> -				if (is_slave_b_added)
> -					vlan_vid_del(port->dev, proto, vid);
> -				return ret;
> +				break;
> +			case HSR_PT_SLAVE_B:
> +				netdev_err(dev, "add vid failed for Slave-B\n");
> +				break;
> +			default:
> +				break;
>  			}
>
> -			is_slave_a_added = true;
> +			goto unwind;
> +		}
> +
> +		switch (port->type) {
> +		case HSR_PT_SLAVE_A:
> +			slave_a_dev = port->dev;
>  			break;
>

nit: superflous empty line (it's inconsistent with the other case
blocks)

>  		case HSR_PT_SLAVE_B:
> -			if (ret) {
> -				/* clean up Slave-A */
> -				netdev_err(dev, "add vid failed for Slave-B\n");
> -				if (is_slave_a_added)
> -					vlan_vid_del(port->dev, proto, vid);
> -				return ret;
> -			}
> -
> -			is_slave_b_added = true;
> +			slave_b_dev = port->dev;
>  			break;
>  		default:
>  			break;

I think this would look cleaner with the good and the bad paths in the
same switch-case, but that may be a matter of (my) taste. What do you
think?

Thanks,
   Felix


  reply	other threads:[~2026-03-27 11:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 15:47 [PATCH net-next v2 0/4] net: hsr: address functional and concurrency bugs luka.gejak
2026-03-26 15:47 ` [PATCH net-next v2 1/4] net: hsr: serialize seq_blocks merge across nodes luka.gejak
2026-03-26 15:47 ` [PATCH net-next v2 2/4] net: hsr: fix VLAN add unwind on slave errors luka.gejak
2026-03-27 11:52   ` Felix Maurer [this message]
2026-03-27 16:03     ` Luka Gejak
2026-03-27 18:39       ` Felix Maurer
2026-03-26 15:47 ` [PATCH net-next v2 3/4] net: hsr: require valid EOT supervision TLV luka.gejak
2026-03-26 15:47 ` [PATCH net-next v2 4/4] net: hsr: reject unresolved interlink ifindex luka.gejak

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=acZvYp_SYvypHWgk@thinkpad \
    --to=fmaurer@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=luka.gejak@linux.dev \
    --cc=netdev@vger.kernel.org \
    --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