From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, pshelar@nicira.com, cwang@twopensource.com,
nicolas.dichtel@6wind.com, ebiederm@xmission.com,
david@gibson.dropbear.id.au, sfeldma@cumulusnetworks.com,
sucheta.chakraborty@qlogic.com, stephen@networkplumber.org
Subject: [patch net-next 1/2] rtnetlink: allow to register ops without ops->setup set
Date: Wed, 25 Jun 2014 14:27:59 +0200 [thread overview]
Message-ID: <1403699280-12837-1-git-send-email-jiri@resnulli.us> (raw)
So far, it is assumed that ops->setup is filled up. But there might be
case that ops might make sense even without ->setup. In that case,
forbid to newlink and dellink.
Signed-off-by: Jiri Pirko <jiri@resnulli.us>
---
net/core/rtnetlink.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
index 1063996..84affd7 100644
--- a/net/core/rtnetlink.c
+++ b/net/core/rtnetlink.c
@@ -1777,7 +1777,7 @@ static int rtnl_dellink(struct sk_buff *skb, struct nlmsghdr *nlh)
return -ENODEV;
ops = dev->rtnl_link_ops;
- if (!ops)
+ if (!ops || !ops->setup)
return -EOPNOTSUPP;
ops->dellink(dev, &list_kill);
@@ -2038,6 +2038,9 @@ replay:
return -EOPNOTSUPP;
}
+ if (!ops->setup)
+ return -EOPNOTSUPP;
+
if (!ifname[0])
snprintf(ifname, IFNAMSIZ, "%s%%d", ops->kind);
--
1.9.0
next reply other threads:[~2014-06-25 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 12:27 Jiri Pirko [this message]
2014-06-25 12:28 ` [patch net-next 2/2] openvswitch: introduce rtnl ops stub Jiri Pirko
2014-06-25 16:02 ` Eric W. Biederman
2014-06-25 16:35 ` Jiri Pirko
2014-06-25 17:13 ` Eric W. Biederman
2014-06-26 7:39 ` Jiri Pirko
2014-06-25 15:55 ` [patch net-next 1/2] rtnetlink: allow to register ops without ops->setup set Eric W. Biederman
2014-06-25 16:31 ` Jiri Pirko
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=1403699280-12837-1-git-send-email-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=david@gibson.dropbear.id.au \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pshelar@nicira.com \
--cc=sfeldma@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=sucheta.chakraborty@qlogic.com \
/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;
as well as URLs for NNTP newsgroup(s).