netdev - DSA .port_{f,m}db_{add,del} with offloaded LAG interface on mv88e6xxx

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALW65jZoaYYycAApviuQjiOTNuG9sfSpGZ1izRgJhj4M-gfDyQ@mail.gmail.com>
Date:   Mon, 19 Jul 2021 20:22:01 +0800
From:   DENG Qingfang <dqfext@...il.com>
To:     netdev <netdev@...r.kernel.org>
Cc:     Vladimir Oltean <olteanv@...il.com>, Andrew Lunn <andrew@...n.ch>,
        Marek Behún <kabel@...nel.org>,
        Tobias Waldekranz <tobias@...dekranz.com>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Russell King - ARM Linux admin <linux@...linux.org.uk>,
        Florian Fainelli <f.fainelli@...il.com>
Subject: DSA .port_{f,m}db_{add,del} with offloaded LAG interface on mv88e6xxx

Hi,

What happens if a FDB entry is added manually to an offloaded LAG
interface? Does DSA core simply call .port_fdb_add with the member
ports in the LAG?

I'm asking because there is a trunk field in struct
mv88e6xxx_atu_entry, when it is true, the portvec is actually the
trunk ID.
As the current implementation (mv88e6xxx_port_db_load_purge) does not
use this field, it probably won't work.

Regards,
Qingfang