From: luka.gejak@linux.dev
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Cc: horms@kernel.org, fmaurer@redhat.com, liuhangbin@gmail.com,
bigeasy@linutronix.de, linux-kernel@vger.kernel.org,
Luka Gejak <luka.gejak@linux.dev>
Subject: [PATCH net-next v1 2/4] net: hsr: fix VLAN add unwind on slave errors
Date: Tue, 24 Mar 2026 15:35:01 +0100 [thread overview]
Message-ID: <20260324143503.187642-3-luka.gejak@linux.dev> (raw)
In-Reply-To: <20260324143503.187642-1-luka.gejak@linux.dev>
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 ensuring the cleanup path targets the previously
programmed slave device when the second slave fails to add the VID.
Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
---
net/hsr/hsr_device.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/net/hsr/hsr_device.c b/net/hsr/hsr_device.c
index 5c3eca2235ce..6185f9f2630f 100644
--- a/net/hsr/hsr_device.c
+++ b/net/hsr/hsr_device.c
@@ -534,6 +534,8 @@ static int hsr_ndo_vlan_rx_add_vid(struct net_device *dev,
{
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;
@@ -552,11 +554,12 @@ static int hsr_ndo_vlan_rx_add_vid(struct net_device *dev,
/* clean up Slave-B */
netdev_err(dev, "add vid failed for Slave-A\n");
if (is_slave_b_added)
- vlan_vid_del(port->dev, proto, vid);
+ vlan_vid_del(slave_b_dev, proto, vid);
return ret;
}
is_slave_a_added = true;
+ slave_a_dev = port->dev;
break;
case HSR_PT_SLAVE_B:
@@ -564,11 +567,12 @@ static int hsr_ndo_vlan_rx_add_vid(struct net_device *dev,
/* 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);
+ vlan_vid_del(slave_a_dev, proto, vid);
return ret;
}
is_slave_b_added = true;
+ slave_b_dev = port->dev;
break;
default:
break;
--
2.53.0
next prev parent reply other threads:[~2026-03-24 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 14:34 [PATCH net-next v1 0/4] net: hsr: address functional and concurrency bugs luka.gejak
2026-03-24 14:35 ` [PATCH net-next v1 1/4] net: hsr: serialize seq_blocks merge across nodes luka.gejak
2026-03-26 14:28 ` Felix Maurer
2026-03-24 14:35 ` luka.gejak [this message]
2026-03-26 14:29 ` [PATCH net-next v1 2/4] net: hsr: fix VLAN add unwind on slave errors Felix Maurer
2026-03-24 14:35 ` [PATCH net-next v1 3/4] net: hsr: require valid EOT supervision TLV luka.gejak
2026-03-26 14:29 ` Felix Maurer
2026-03-24 14:35 ` [PATCH net-next v1 4/4] net: hsr: reject unresolved interlink ifindex luka.gejak
2026-03-26 14:30 ` Felix Maurer
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=20260324143503.187642-3-luka.gejak@linux.dev \
--to=luka.gejak@linux.dev \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmaurer@redhat.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--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