[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1455312860-24666-1-git-send-email-vivien.didelot@savoirfairelinux.com>
Date: Fri, 12 Feb 2016 16:34:17 -0500
From: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To: netdev@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kernel@...oirfairelinux.com,
"David S. Miller" <davem@...emloft.net>,
Jiri Pirko <jiri@...nulli.us>,
Scott Feldman <sfeldma@...il.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
Ido Schimmel <idosch@...lanox.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Subject: [PATCH RFC 0/3] net: bridge: set forwarding state when unbridging switchdev ports
When a port leaves a bridge, the bridge layer sets its STP state to Disabled.
But switchdev users seem to need to restore its state to Forwarding to keep the
communication with the CPU port functional (see DSA and Rocker for instance).
br_set_state() tries to set the switchdev port state, if correctly implemented.
So call it within del_nbp() to restore the Forwarding state on port removal.
Does that make sense or are there scenarios where we don't want this behavior?
Thanks,
Vivien Didelot (3):
net: bridge: log state when setting it
net: bridge: set forwarding state on port removal
net: dsa: remove dsa_slave_stp_update
net/bridge/br_if.c | 5 +++++
net/bridge/br_stp.c | 5 ++---
net/dsa/slave.c | 17 -----------------
3 files changed, 7 insertions(+), 20 deletions(-)
--
2.7.1
Powered by blists - more mailing lists