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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 21 Apr 2022 09:38:03 +0200
From:   Clément Léger <>
To:     Vladimir Oltean <>
Cc:     Andrew Lunn <>,
        Vivien Didelot <>,
        Florian Fainelli <>,
        "David S . Miller" <>,
        Jakub Kicinski <>,
        Paolo Abeni <>,
        Rob Herring <>,
        Krzysztof Kozlowski <>,
        Geert Uytterhoeven <>,
        Magnus Damm <>,
        Heiner Kallweit <>,
        Russell King <>,
        Thomas Petazzoni <>,
        Herve Codina <>,
        Miquèl Raynal <>,
        Milan Stevanovic <>,
        Jimmy Lalande <>,,,,
Subject: Re: [PATCH net-next 08/12] net: dsa: rzn1-a5psw: add FDB support

Le Wed, 20 Apr 2022 22:52:14 +0300,
Vladimir Oltean <> a écrit :

> > > 
> > > Shouldn't this contain something along the lines of a VID, FID, something?  
> > 
> > This is extracted directly from the datasheet [1]. The switch FDB table
> > does not seems to store the VID with the entries (See page 300).
> > 
> > [1]
> >  
> Thanks for the link. I see that the switch has a non-partitionable
> lookup table, not even by VLAN. A shame.
> This is also in contrast with the software bridge driver, where FDB and
> MDB entries can have independent destinations per VID.
> So there's nothing you can do beyond limiting to a single offloaded
> bridge and hoping for the best w.r.t. per-VLAN forwarding destinations.
> Note that if you limit to a single bridge does not mean that you can
> declare ds->fdb_isolation = true. Declaring that would opt you into
> unicast and multicast filtering towards the CPU, i.o.w. a method for
> software to only receive the addresses it has expressed an interest in,
> rather than all packets received on standalone ports. The way that is
> implemented in DSA is by adding FDB and MDB entries on the management
> port, and it would break a lot of things without a partitioning scheme
> for the lookup table.

Thanks Vladimir, it confirms what I thought.

Clément Léger,
Embedded Linux and Kernel engineer at Bootlin

Powered by blists - more mailing lists