From: Vladislav Yasevich <[email protected]> Date: Tue, 4 Apr 2017 09:23:40 -0400
> 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. > > V2: Added missed events (from David Ahern) Series applied, thanks Vlad.
