rtnetlink: bring NETDEV_POST_TYPE_CHANGE event process back in rtnetlink_event
authorXin Long <lucien.xin@gmail.com>
Sun, 15 Oct 2017 10:13:43 +0000 (18:13 +0800)
committerDavid S. Miller <davem@davemloft.net>
Mon, 16 Oct 2017 19:48:45 +0000 (20:48 +0100)
As I said in patch 'rtnetlink: bring NETDEV_CHANGEMTU event process back
in rtnetlink_event', removing NETDEV_POST_TYPE_CHANGE event was not the
right fix for the redundant notifications issue.

So bring this event process back to rtnetlink_event and the old redundant
notifications issue would be fixed in the later patch 'rtnetlink: check
DO_SETLINK_NOTIFY correctly in do_setlink'.

Fixes: aef091ae58aa ("rtnetlink: Do not generate notifications for POST_TYPE_CHANGE event")
Signed-off-by: Xin Long <lucien.xin@gmail.com>
Acked-by: David Ahern <dsahern@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/core/rtnetlink.c

index bf47360..8e44fd5 100644 (file)
@@ -4284,6 +4284,7 @@ static int rtnetlink_event(struct notifier_block *this, unsigned long event, voi
        case NETDEV_CHANGENAME:
        case NETDEV_FEAT_CHANGE:
        case NETDEV_BONDING_FAILOVER:
+       case NETDEV_POST_TYPE_CHANGE:
        case NETDEV_NOTIFY_PEERS:
        case NETDEV_RESEND_IGMP:
        case NETDEV_CHANGEINFODATA: