From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladislav Yasevich Subject: [PATCH v2 net-next 0/2] rtnetlink: Updates to rtnetlink_event() Date: Tue, 4 Apr 2017 09:23:40 -0400 Message-ID: <1491312223-18772-1-git-send-email-vyasevic@redhat.com> Cc: roopa@cumulusnetworks.com, dsa@cumulusnetworks.com, davem@davemloft.net, Vladislav Yasevich To: netdev@vger.kernel.org Return-path: Received: from mail-qt0-f194.google.com ([209.85.216.194]:36736 "EHLO mail-qt0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753075AbdDDNYM (ORCPT ); Tue, 4 Apr 2017 09:24:12 -0400 Received: by mail-qt0-f194.google.com with SMTP id n37so23214120qtb.3 for ; Tue, 04 Apr 2017 06:24:12 -0700 (PDT) Sender: netdev-owner@vger.kernel.org List-ID: 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) 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 | 21 ++++++++ net/core/dev.c | 2 +- net/core/rtnetlink.c | 121 +++++++++++++++++++++++++++++++++++-------- 4 files changed, 123 insertions(+), 24 deletions(-) -- 2.7.4