netdev - Re: [PATCH net-next v2 00/13] Change DSA's FDB API and perform switchdev cleanup

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87mv80ji63.fsf@weeman.i-did-not-set--mail-host-address--so-tickle-me>
Date:   Wed, 19 Jul 2017 16:17:08 -0400
From:   Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To:     Arkadi Sharshevsky <arkadis@...lanox.com>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, jiri@...nulli.us, ivecera@...hat.com,
        f.fainelli@...il.com, andrew@...n.ch, Woojung.Huh@...rochip.com,
        stephen@...workplumber.org, mlxsw@...lanox.com,
        Arkadi Sharshevsky <arkadis@...lanox.com>
Subject: Re: [PATCH net-next v2 00/13] Change DSA's FDB API and perform switchdev cleanup

Hi Arkadi,

I am testing your patch series the behavior changes suspiciously:

    # brctl show br0
    bridge name	bridge id		STP enabled	interfaces
    br0		8000.f6d5ef06ccdd	no		lan0
                                                        lan1
                                                        lan2
                                                        lan3
                                                        lan4
                                                        lan5
                                                        lan6
                                                        lan7
                                                        lan8
                                                        optical3
                                                        optical4

Without the patchset I have this behavior:

    # bridge fdb add 00:11:22:33:44:55 dev lan4
    # bridge fdb add 22:33:44:55:66:77 dev lan2 self
    # bridge fdb show                               
    01:00:5e:00:00:01 dev eth0 self permanent
    01:00:5e:00:00:01 dev eth1 self permanent
    0a:3f:f6:06:a2:ee dev lan0 master br0 permanent
    22:33:44:55:66:77 dev lan2 self static
    00:11:22:33:44:55 dev lan4 self static
    01:00:5e:00:00:01 dev br0 self permanent

And now with the patchset applied I have:

# bridge fdb add 00:11:22:33:44:55 dev lan4
# bridge fdb add 22:33:44:55:66:77 dev lan2 self
# bridge fdb show
01:00:5e:00:00:01 dev eth0 self permanent
00:11:22:33:44:55 dev eth1 self permanent
22:33:44:55:66:77 dev eth1 self permanent
01:00:5e:00:00:01 dev eth1 self permanent
0a:ca:c8:6b:05:65 dev lan0 master br0 permanent
01:00:5e:00:00:01 dev br0 self permanent


It looks like the FDB entries are reported to be associated with the
master net device (eth1). Is the dump broken or is it the whole add?

Thanks,

        Vivien