netdev - [BUG] iproute2 - vlan-ids not shown when -details used

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

Message-ID: <1055ba5b-7230-466a-ba6d-4bc946c908c0@gmail.com>
Date: Tue, 30 Apr 2024 19:27:08 +0200
From: Antonio Prcela <antonio.prcela@...il.com>
To: netdev@...r.kernel.org
Subject: [BUG] iproute2 - vlan-ids not shown when -details used

Hi,

the following bug has been found in iproute2's bridge tool. Reproduced with
v6.8.0 running on kernel v6.8.8 and v5.17.0 running on kernel v5.15.70

Create a bridge and attach eth1 to it. Set vlan-ids, for example 10-15,
set PVID of eth1 to something different than 1 but keep it inbetween the
set vlan-ids. Ergo: if vlan-id 10-15 set, then: PVID > 10 && PVID < 15.

Query the state via bridge vlan show:

$ bridge vlan show dev eth1
port              vlan-id
eth1              10
                  11
                  12
                  13 PVID
                  14
                  15

Query the state by adding -details flag:

$ bridge -details vlan show dev eth1
port              vlan-id
eth1              10-12
                    state forwarding mcast_router 1 neigh_suppress off
                  13 PVID
                    state forwarding mcast_router 1 neigh_suppress off

As one can see, the -details basically stops at the PVID and doesn't
show any vlan-id(s) that come afterwards.

This issue can also be reproduced in a standalone program that uses
BRIDGE_VLANDB_*, like it's within iproute2 when -details is used.
Whereas not using -details retreives the vlan-ids via IFLA_AF_SPEC
and that works fine.

Unfortunatley I do not fully understand iproute2 'under te hood' to
provide a patch which would fix this issue.

Hoping for some feedback regarding this. Might be 'works as designed'?

Regards,
Antonio P.