[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1491013654-395-1-git-send-email-vyasevic@redhat.com>
Date: Fri, 31 Mar 2017 22:27:32 -0400
From: Vladislav Yasevich <vyasevich@...il.com>
To: netdev@...r.kernel.org
Cc: roopa@...ulusnetworks.com, dsa@...ulusnetworks.com,
davem@...emloft.net, Vladislav Yasevich <vyasevic@...hat.com>
Subject: [PATCH net-next 0/2] rtnetlink: Updates to rtnetlink_event()
This series came out of the conversation that started as a result
my first attempt to add netdevice event info to netlink messages.
This series converts event processing to a 'white list', where
we explicitely permit events to generate netlink messages. This
is meant to make people take a closer look and determine wheter
these events should really trigger netlink messages.
I am also adding a V2 of my patch to add event type to the netlink
message. This version supports all events that we currently generate.
I will also update my patch to iproute that will show this data
through 'ip monitor'.
I actually need the ability to trap NETDEV_NOTIFY_PEERS event
(as well as possible NETDEV_RESEND_IGMP) to support hanlding of
macvtap on top of bonding. I hope others will also find this info usefull.
Vladislav Yasevich (2):
rtnetlink: Convert rtnetlink_event to white list
rtnl: Add support for netdev event to link messages
include/linux/rtnetlink.h | 3 +-
include/uapi/linux/if_link.h | 19 ++++++++
net/core/dev.c | 2 +-
net/core/rtnetlink.c | 113 ++++++++++++++++++++++++++++++++++---------
4 files changed, 113 insertions(+), 24 deletions(-)
--
2.7.4
Powered by blists - more mailing lists