Netdev List
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: [iproute PATCH] iplink: Notify user if EEXIST error might be spurious
Date: Tue,  1 Aug 2017 19:27:47 +0200	[thread overview]
Message-ID: <20170801172747.2817-1-phil@nwl.cc> (raw)

Back in the days when RTM_NEWLINK wasn't yet implemented, people had to
rely upon kernel modules to create (virtual) interfaces for them. The
number of those was usually defined via module parameter, and a sane
default value was chosen. Now that iproute2 allows users to instantiate
new interfaces at will, this is no longer required - though for
backwards compatibility reasons, we're stuck with both methods which
collide at the point when one tries to create an interface with a
standard name for a type which exists in a kernel module: The kernel
will load the module, which instantiates the interface and the following
RTM_NEWLINK request will fail since the interface exists already. For
instance:

| # lsmod | grep dummy
| # ip link show | grep dummy0
| # ip link add dummy0 type dummy
| RTNETLINK answers: File exists
| # ip link show | grep -c dummy0
| 1

There is no race-free solution in userspace for this dilemma as far as I
can tell, so try to detect whether a user might have run into this and
notify that the given error message might be irrelevant.

Signed-off-by: Phil Sutter <phil@nwl.cc>
---
 ip/iplink.c | 35 ++++++++++++++++++++++++++++++++++-
 1 file changed, 34 insertions(+), 1 deletion(-)

diff --git a/ip/iplink.c b/ip/iplink.c
index 5aff2fde38dae..f94fa96668d21 100644
--- a/ip/iplink.c
+++ b/ip/iplink.c
@@ -867,6 +867,33 @@ int iplink_parse(int argc, char **argv, struct iplink_req *req,
 	return ret - argc;
 }
 
+static bool link_name_is_standard(const char *type, const char *name)
+{
+	const struct {
+		const char *type;
+		const char *name;
+	} standard_links[] = {
+		{ "dummy", "dummy0" },
+		{ "ifb", "ifb0" },
+		{ "ifb", "ifb1" },
+		{ "bond", "bond0" },
+		{ "ipip", "tunl0" },
+		{ "gre", "gre0" },
+		{ "gretap", "gretap0" },
+		{ "vti", "ip_vti0" },
+		{ "sit", "sit0" },
+	};
+	int i;
+
+	for (i = 0; i < ARRAY_SIZE(standard_links); i++) {
+		if (strcmp(type, standard_links[i].type) ||
+		    strcmp(name, standard_links[i].name))
+			continue;
+		return true;
+	}
+	return false;
+}
+
 static int iplink_modify(int cmd, unsigned int flags, int argc, char **argv)
 {
 	int len;
@@ -1007,8 +1034,14 @@ static int iplink_modify(int cmd, unsigned int flags, int argc, char **argv)
 		return -1;
 	}
 
-	if (rtnl_talk(&rth, &req.n, NULL, 0) < 0)
+	if (rtnl_talk(&rth, &req.n, NULL, 0) < 0) {
+		if (errno == EEXIST &&
+		    flags & NLM_F_CREATE &&
+		    link_name_is_standard(type, name))
+			fprintf(stderr,
+				"Note: Kernel might have created interface upon module load.\n");
 		return -2;
+	}
 
 	return 0;
 }
-- 
2.13.1

             reply	other threads:[~2017-08-01 17:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 17:27 Phil Sutter [this message]
2017-08-03 22:52 ` [iproute PATCH] iplink: Notify user if EEXIST error might be spurious Stephen Hemminger

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=20170801172747.2817-1-phil@nwl.cc \
    --to=phil@nwl.cc \
    --cc=netdev@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox