netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladislav Yasevich <vyasevich@gmail.com>
To: netdev@vger.kernel.org
Cc: dsa@cumulusnetworks.com, Vladislav Yasevich <vyasevic@redhat.com>
Subject: [PATCH net-next 1/2] rtnetlink: Disable notification for NETDEV_NAMECHANGE event
Date: Fri, 21 Apr 2017 13:31:20 -0400	[thread overview]
Message-ID: <1492795881-11914-2-git-send-email-vyasevic@redhat.com> (raw)
In-Reply-To: <1492795881-11914-1-git-send-email-vyasevic@redhat.com>

The data signaling name change is already provided at
the end of do_setlink().  This event handler just generates
a duplicate announcement.  Disable it.

CC: David Ahern <dsa@cumulusnetworks.com>
Signed-off-by: Vladislav Yasevich <vyasevic@redhat.com>
---
 net/core/rtnetlink.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
index 0ee5479..e8e6816 100644
--- a/net/core/rtnetlink.c
+++ b/net/core/rtnetlink.c
@@ -4123,7 +4123,6 @@ static int rtnetlink_event(struct notifier_block *this, unsigned long event, voi
 
 	switch (event) {
 	case NETDEV_REBOOT:
-	case NETDEV_CHANGENAME:
 	case NETDEV_FEAT_CHANGE:
 	case NETDEV_BONDING_FAILOVER:
 	case NETDEV_NOTIFY_PEERS:
-- 
2.7.4

  reply	other threads:[~2017-04-21 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 17:31 [PATCH v3 net-next 0/2] rtnetlink: Updates to rtnetlink_event() Vladislav Yasevich
2017-04-21 17:31 ` Vladislav Yasevich [this message]
2017-04-21 18:08   ` [PATCH net-next 1/2] rtnetlink: Disable notification for NETDEV_NAMECHANGE event David Ahern
2017-04-27 19:26     ` Vlad Yasevich
2017-04-21 17:31 ` [PATCH net-next V3 2/2] rtnl: Add support for netdev event attribute to link messages Vladislav Yasevich
2017-04-24  1:07   ` David Ahern
2017-04-24 15:14     ` Roopa Prabhu
2017-04-27 19:51       ` Vlad Yasevich
2017-04-28  0:11         ` Roopa Prabhu
2017-04-27 19:43     ` Vlad Yasevich
2017-04-27 19:59       ` David Ahern
2017-04-28 16:38         ` Jiri Pirko
2017-05-01 13:35           ` Vlad Yasevich
2017-05-02 21:57             ` David Ahern

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=1492795881-11914-2-git-send-email-vyasevic@redhat.com \
    --to=vyasevich@gmail.com \
    --cc=dsa@cumulusnetworks.com \
    --cc=netdev@vger.kernel.org \
    --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).