netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladislav Yasevich <vyasevich@gmail.com>
To: netdev@vger.kernel.org
Cc: roopa@cumulusnetworks.com, dsa@cumulusnetworks.com,
	davem@davemloft.net, Vladislav Yasevich <vyasevic@redhat.com>
Subject: [PATCH net-next 0/2] rtnetlink: Updates to rtnetlink_event()
Date: Tue,  4 Apr 2017 09:23:43 -0400	[thread overview]
Message-ID: <1491312223-18772-4-git-send-email-vyasevic@redhat.com> (raw)
In-Reply-To: <1491312223-18772-1-git-send-email-vyasevic@redhat.com>

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

  parent reply	other threads:[~2017-04-04 13:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 13:23 [PATCH v2 net-next 0/2] rtnetlink: Updates to rtnetlink_event() Vladislav Yasevich
2017-04-04 13:23 ` [PATCH v2 net-next 1/2] rtnetlink: Convert rtnetlink_event to white list Vladislav Yasevich
2017-04-04 13:23 ` [PATCH v2 net-next 2/2] rtnl: Add support for netdev event to link messages Vladislav Yasevich
2017-04-04 13:23 ` Vladislav Yasevich [this message]
2017-04-05 15:14 ` [PATCH v2 net-next 0/2] rtnetlink: Updates to rtnetlink_event() David Miller
  -- strict thread matches above, loose matches on Subject: below --
2017-04-01  2:27 [PATCH " Vladislav Yasevich

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=1491312223-18772-4-git-send-email-vyasevic@redhat.com \
    --to=vyasevich@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=vyasevic@redhat.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).