From: Vlad Yasevich <vyasevic@redhat.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Stephen Hemminger <shemminger@vyatta.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [RFC] bridge and friends: reduce TheLinuxWay(tm)
Date: Wed, 16 Oct 2013 16:22:08 -0400 [thread overview]
Message-ID: <525EF570.3050105@redhat.com> (raw)
In-Reply-To: <525EF4E7.1030003@mojatatu.com>
On 10/16/2013 04:19 PM, Jamal Hadi Salim wrote:
>
> And another little glitch, iflink specifies
>
> [IFLA_AF_SPEC] = {
> [AF_INET] = {
> [IFLA_INET_CONF] = ...,
> },
> [AF_INET6] = {
> [IFLA_INET6_FLAGS] = ...,
> [IFLA_INET6_CONF] = ...,
> }
>
> But then bridge hijacks it and specifies:
> [IFLA_AF_SPEC] = {
> [IFLA_BRIDGE_FLAGS]
> [IFLA_BRIDGE_MODE]
> [IFLA_BRIDGE_VLAN_INFO]
> }
>
> Was that intended as:
>
> [IFLA_AF_SPEC] = {
> [AF_BRIDGE] = {
> [IFLA_BRIDGE_FLAGS]
> [IFLA_BRIDGE_MODE]
> [IFLA_BRIDGE_VLAN_INFO]
> }
> }
>
> Now granted that bridging uses PF_BRIDGE as the family and iflink uses
> PF_UNSPEC - but i do think this one is polluting the namespace.
>
Yes, I know about that one. BRIDGE_FLAGS started the polution and then
we continued it with the other attributes....
-vlad
> cheers,
> jamal
next prev parent reply other threads:[~2013-10-16 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 21:32 [RFC] bridge and friends: reduce TheLinuxWay(tm) Jamal Hadi Salim
2013-10-14 21:41 ` Stephen Hemminger
2013-10-16 13:54 ` Jamal Hadi Salim
2013-10-16 14:05 ` Jamal Hadi Salim
2013-10-16 17:11 ` Vlad Yasevich
2013-10-16 17:49 ` Jamal Hadi Salim
2013-10-16 18:35 ` Eric Dumazet
2013-10-16 18:49 ` Stephen Hemminger
2013-10-16 18:50 ` Vlad Yasevich
2013-10-16 19:02 ` Jamal Hadi Salim
2013-10-16 20:19 ` Jamal Hadi Salim
2013-10-16 20:22 ` Vlad Yasevich [this message]
2013-10-18 10:42 ` Jamal Hadi Salim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525EF570.3050105@redhat.com \
--to=vyasevic@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.