netdev - Re: Vlan interface nuisance

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:	Tue, 3 Mar 2009 06:41:49 +0000
From:	Jarek Poplawski <jarkao2@...il.com>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Stephen Hemminger <shemminger@...tta.com>,
	netdev@...r.kernel.org
Subject: Re: Vlan interface nuisance

On Tue, Mar 03, 2009 at 12:35:00AM +0100, Patrick McHardy wrote:
> Jarek Poplawski wrote:
>> On Mon, Mar 02, 2009 at 10:49:18PM +0100, Patrick McHardy wrote:
>>> The binding is displayed when listing interfaces. This hole
>>> argument is silly, if you want a particular name, just specify
>>> it. The current naming schemes are entirely based on information
>>> that you have to specify anyways.
>>
>> Just for the record, I don't agree with calling "this" argument silly
>> just like it was with "that" argument. Actually, I think they are
>> both so "right" that I've changed my mind and think it's great each
>> tool does it differently...
>
> I'm not sure whether I'm supposed to understand this, so I'm going
> to respond with something useful unrelated to naming user resources
> that every virtual device author should know (and that seems to be
> not well known):
>
> Every virtual device bound to a different device should set the
> dev->iflink field to the ifindex of the device bound to. This
> makes every device related netlink message include this relation.
> If the binding is already known at device-creation time and
> relevant for the virtuals device's existance, this must be done
> in the ->init callback to make sure its already included in the
> first netlink creation message to avoid inconsistent information.
>
> This is the also the prefered way device bindings should be
> signaled to the kernel, and at least iproute and libnl are
> aware of this in both directions. And to get back to the main
> point of this discussion:
>
> # ip l l
> 4: vlan0@...my0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN
>     link/ether 92:2a:4f:ae:dc:29 brd ff:ff:ff:ff:ff:ff

Yes, very interesting arguments for another disussion... But if we're
talking about naming than you seem to ignore what Lennart, Ben, Denys
and probably Stephen said about their preferred way, and I think it
matters, because if they had problems with understanding this change
I can only imagine what "common users" would say without knowing all
this technical rationale (which IMHO is disputable too - names  are
for people).

Jarek P.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html