From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Thode <mthode@mthode.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] colons are invalid characters in netdev names
Date: Tue, 17 Feb 2015 19:28:03 -0600 [thread overview]
Message-ID: <20150217192803.21a63afd@uryu.home.lan> (raw)
In-Reply-To: <1424214942-17581-1-git-send-email-mthode@mthode.org>
On Tue, 17 Feb 2015 17:15:42 -0600
Matthew Thode <mthode@mthode.org> wrote:
> colons are used as a separator in netdev device lookup in dev_ioctl.c
>
> Specific functions are SIOCGIFTXQLEN SIOCETHTOOL SIOCSIFNAME
>
> Signed-off-by: Matthew Thode <mthode@mthode.org>
What is the exact sequence that causes the problem?
SIOCSIFNAME already strips of colon.
next prev parent reply other threads:[~2015-02-18 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 23:15 Matthew Thode
2015-02-17 23:46 ` Lino Sanfilippo
2015-02-17 23:57 ` Matthew Thode
2015-02-18 0:13 ` Lino Sanfilippo
2015-02-18 1:28 ` Stephen Hemminger [this message]
2015-02-18 1:33 ` Matthew Thode
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=20150217192803.21a63afd@uryu.home.lan \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mthode@mthode.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®