From: David Ahern <dsahern@gmail.com>
To: nicolas.dichtel@6wind.com
Cc: David Miller <davem@redhat.com>,
stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: hide devices starting with period by default
Date: Thu, 4 May 2017 10:37:39 -0600 [thread overview]
Message-ID: <4bbb7a19-1b0b-8c9a-7e74-82ee146cf48c@gmail.com> (raw)
In-Reply-To: <0635d3bb-0d8d-7ab6-fb53-4d84f979a023@6wind.com>
On 5/4/17 9:15 AM, Nicolas Dichtel wrote:
> Le 24/02/2017 à 16:52, David Ahern a écrit :
>> On 2/23/17 8:12 PM, David Miller wrote:
>>> This really need to be a fundamental facility, so that it transparently
>>> works for NetworkManager, router daemons, everything. Not just iproute2
>>> and "ls".
>>
>> I'll rebase my patch and send out as RFC.
>>
> David, did you finally send those patches?
>
No, but for a few reasons.
It is easy to hide devices in a dump:
https://github.com/dsahern/linux/commit/48a80a00eac284e58bae04af10a5a932dd7aee00
But I think those devices should also not exist in sysfs or procfs which
overlaps what I would like to see for lightweight netdevices:
https://github.com/dsahern/linux/commit/70574be699cf252e77f71e3df11192438689f976
and to be complete, hidden devices should not be allowed to have a
network address or transmit packets which is the L2 only intent from
Florian:
https://www.spinics.net/lists/netdev/msg340808.html
next prev parent reply other threads:[~2017-05-04 16:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 19:50 [PATCH] iproute2: hide devices starting with period by default Stephen Hemminger
2017-02-23 23:39 ` David Ahern
2017-02-24 0:30 ` Stephen Hemminger
2017-02-24 1:07 ` David Ahern
2017-02-24 1:31 ` Stephen Hemminger
2017-02-24 15:38 ` Phil Sutter
2017-02-24 3:12 ` David Miller
2017-02-24 15:52 ` David Ahern
2017-05-04 15:15 ` Nicolas Dichtel
2017-05-04 16:37 ` David Ahern [this message]
2017-05-04 19:10 ` Florian Fainelli
2017-05-04 19:47 ` David Ahern
2017-05-05 6:47 ` Jiri Benc
2017-05-05 7:42 ` Nicolas Dichtel
2017-02-24 17:06 ` Andy Gospodarek
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=4bbb7a19-1b0b-8c9a-7e74-82ee146cf48c@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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.