netdev - Re: [PATCH iproute2 net-next 2/5] bridge: add json support for bridge vlan show

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]

Date:	Mon, 30 May 2016 09:43:07 +0900
From:	Toshiaki Makita <makita.toshiaki@....ntt.co.jp>
To:	Roopa Prabhu <roopa@...ulusnetworks.com>,
	stephen@...workplumber.org, netdev@...r.kernel.org
Cc:	anuradhak@...ulusnetworks.com, nikolay@...ulusnetworks.com,
	julien@...ulusnetworks.com
Subject: Re: [PATCH iproute2 net-next 2/5] bridge: add json support for bridge
 vlan show

On 2016/05/28 13:37, Roopa Prabhu wrote:
> From: Roopa Prabhu <roopa@...ulusnetworks.com>
> 
> $bridge -c vlan show
> port	vlan ids
> swp1	 1 PVID Egress Untagged
> 	 10-13
> 
> swp2	 1 PVID Egress Untagged
> 	 10-13
> 
> br0	 1 PVID Egress Untagged
> 
> $bridge -j vlan show
> {
>     "swp1": [{
>             "vlan": 1,
>             "flags": "PVID Egress Untagged"

Shouldn't we split flags?

    "swp1": [{
            "vlan": 1,
            "flags": [
                "PVID",
                "Egress Untagged"
            ]
        }

--
Toshiaki Makita