lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191217112122.GB17965@lunn.ch>
Date:   Tue, 17 Dec 2019 12:21:22 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Murali Karicheri <m-karicheri2@...com>
Cc:     netdev@...r.kernel.org, "Kwok, WingMan" <w-kwok2@...com>,
        vivien.didelot@...il.com, f.fainelli@...il.com, jiri@...nulli.us,
        ivecera@...hat.com
Subject: Re: RSTP with switchdev question

On Mon, Dec 16, 2019 at 11:55:05AM -0500, Murali Karicheri wrote:
> + switchdev/DSA experts

Hi Murali

I did not reply before because this is a pure switchdev issue. DSA
does things differently. The kernel FDB and the switches FDB are not
kept in sync. With DSA, when a port changes state, we flush the switch
FDB. For STP, that seems to be sufficient. There have been reports for
RSTP this might not be enough, but that conversation did not go very
far.

I've no idea how this is supposed to work with a pure switchdev
driver. Often, to answer a question like this, you need to take a step
backwards. How is this supposed to work for a machine with two e1000e
cards and a plain software bridge? What ever APIs user space RSTP is
using in a pure software case should be used in a switchdev setup as
well, but extra plumbing in the kernel might be required, and it
sounds like it may be missing...

      Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ