From: Patrick McHardy <kaber@trash•net>
To: netdev@vger•kernel.org
Cc: Patrick McHardy <kaber@trash•net>
Subject: net: rtnetlink: support specifying device flags on device creation
Date: Fri, 26 Feb 2010 17:34:49 +0100 (MET) [thread overview]
Message-ID: <20100226163449.11434.13013.sendpatchset@x2.localnet> (raw)
The following patches add support to specify the device flags (like UP) when
creating a new device through rtnl_link. This requires to surpress netlink
notifications until the device is fully configured in order to not confuse
userspace when changing the flags fails and registration has to be undone.
Once the device is configured, a single NEWLINK message with the full state
is sent.
The individual patch changelogs describe the necessary changes in more detail.
drivers/net/veth.c | 15 +++--
include/linux/netdevice.h | 9 ++-
include/net/rtnetlink.h | 2 +
net/core/dev.c | 171 +++++++++++++++++++++++++++++----------------
net/core/rtnetlink.c | 59 ++++++++++++----
5 files changed, 176 insertions(+), 80 deletions(-)
Patrick McHardy (4):
net: rtnetlink: ignore NETDEV_PRE_UP notifier in rtnetlink_event()
net: rtnetlink: handle rtnl_link netlink notifications manually
net: dev: support deferring device flag change notifications
net: rtnetlink: support specifying device flags on device creation
next reply other threads:[~2010-02-26 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 16:34 Patrick McHardy [this message]
2010-02-26 16:34 ` net 01/04: rtnetlink: ignore NETDEV_PRE_UP notifier in rtnetlink_event() Patrick McHardy
2010-02-26 16:34 ` net 02/04: rtnetlink: handle rtnl_link netlink notifications manually Patrick McHardy
2010-02-26 16:34 ` net 03/04: dev: support deferring device flag change notifications Patrick McHardy
2010-02-26 16:34 ` net 04/04: rtnetlink: support specifying device flags on device creation Patrick McHardy
2010-02-27 10:51 ` net: " David Miller
2010-03-01 15:24 ` Patrick McHardy
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=20100226163449.11434.13013.sendpatchset@x2.localnet \
--to=kaber@trash$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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