netdev - Re: [PATCH] iproute2: show network device dependency tree

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: <20170301112228.713bd4d5@griffin>
Date:   Wed, 1 Mar 2017 11:22:28 +0100
From:   Jiri Benc <jbenc@...hat.com>
To:     Zaboj Campula <zaboj.campula@...t.cz>
Cc:     Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Subject: Re: [PATCH] iproute2: show network device dependency tree

On Tue, 28 Feb 2017 20:07:37 +0000, Zaboj Campula wrote:
> Well it is impossible to draw a simple tree showing the configuration
> exactly with all details. May be it is too ambitious to draw a tree
> at all.

I tried that and failed. I didn't want to have something that would
work only "somehow" as that would create confusion instead of helping.
See the example below.

> But neither directory structure is a tree (when consider links)
> and there are a plenty of tools showing directory tree.

Directory structure *is* a tree. Symlinks are a special case, for the
purpose of displaying the tree they're just files. Hardlinks can be
ignored when displaying a tree (because there are no hardlinks to
directories). We don't have any of that.

Consider the very simple case of an interface with two vlan interfaces
and both of them in a bridge.

         vlan0
      /        \
eth0             br0
      \        /
         vlan1

You can't represent this in a tree view. And this is just a very simple
example, in reality it tends to be much more complex.

 Jiri