summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorIdo Schimmel <idosch@mellanox.com>2016-01-27 17:20:16 +0300
committerDavid S. Miller <davem@davemloft.net>2016-01-29 02:55:30 +0300
commit4dc236c31733f5d2a3872c88cf12f607d7d36905 (patch)
tree67757128ebcbf6a448f0d2e78a0168ed5bebc436 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent3b9e9488098a7cd91f4111962a49457cfc6557d2 (diff)
downloadlinux-4dc236c31733f5d2a3872c88cf12f607d7d36905.tar.xz
mlxsw: spectrum: Handle port leaving LAG while bridged
It is possible for a user to remove a port from a LAG device, while the LAG device or VLAN devices on top of it are bridged. In these cases, bridge's teardown sequence is never issued, so we need to take care of it ourselves. When LAG's unlinking event is received by port netdev: 1) Traverse its vPorts list and make those member in a bridge leave it. They will be deleted later by LAG code. 2) Make the port netdev itself leave its bridge if member in one. Fixes: 0d65fc13042f ("mlxsw: spectrum: Implement LAG port join/leave") Signed-off-by: Ido Schimmel <idosch@mellanox.com> Signed-off-by: Jiri Pirko <jiri@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions