From: Vlad Yasevich <vyasevic@redhat.com>
To: David Ahern <dsa@cumulusnetworks.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net
Subject: Re: [PATCH net-next 7/8] rtnetlink: Do not generate notifications for NOTIFY_PEERS event
Date: Sat, 8 Apr 2017 21:37:53 -0400 [thread overview]
Message-ID: <7a5c0cdd-7d9b-a8e9-a27c-591d165b5ab3@redhat.com> (raw)
In-Reply-To: <1491600340-8359-8-git-send-email-dsa@cumulusnetworks.com>
On 04/07/2017 05:25 PM, David Ahern wrote:
> NOTIFY_PEERS is an internal event; do not generate userspace
> notifications.
We actually need this event to support macvtap over bonding
as well as to resolve some issues with VMs using a bonded uplink
on the host.
-vlad
>
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
> ---
> include/uapi/linux/if_link.h | 1 -
> net/core/rtnetlink.c | 4 ----
> 2 files changed, 5 deletions(-)
>
> diff --git a/include/uapi/linux/if_link.h b/include/uapi/linux/if_link.h
> index 4fa3bf3eb21d..8f23e9dde667 100644
> --- a/include/uapi/linux/if_link.h
> +++ b/include/uapi/linux/if_link.h
> @@ -906,7 +906,6 @@ enum {
> IFLA_EVENT_CHANGE_NAME,
> IFLA_EVENT_FEAT_CHANGE,
> IFLA_EVENT_BONDING_FAILOVER,
> - IFLA_EVENT_NOTIFY_PEERS,
> IFLA_EVENT_CHANGE_UPPER,
> IFLA_EVENT_RESEND_IGMP,
> IFLA_EVENT_CHANGE_LOWER_STATE,
> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> index e2b0ec5174e7..d2587aa339c4 100644
> --- a/net/core/rtnetlink.c
> +++ b/net/core/rtnetlink.c
> @@ -1294,9 +1294,6 @@ static int rtnl_fill_link_event(struct sk_buff *skb, unsigned long event)
> case NETDEV_BONDING_FAILOVER:
> rtnl_event = IFLA_EVENT_BONDING_FAILOVER;
> break;
> - case NETDEV_NOTIFY_PEERS:
> - rtnl_event = IFLA_EVENT_NOTIFY_PEERS;
> - break;
> case NETDEV_CHANGEUPPER:
> rtnl_event = IFLA_EVENT_CHANGE_UPPER;
> break;
> @@ -4173,7 +4170,6 @@ 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_NOTIFY_PEERS:
> case NETDEV_CHANGEUPPER:
> case NETDEV_RESEND_IGMP:
> case NETDEV_CHANGELOWERSTATE:
>
next prev parent reply other threads:[~2017-04-09 1:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 21:25 [PATCH net-next 0/8] rtnetlink: Cleanup user notifications for netdev events David Ahern
2017-04-07 21:25 ` [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events David Ahern
2017-04-08 18:06 ` Roopa Prabhu
2017-04-08 18:13 ` David Ahern
2017-04-08 18:18 ` Roopa Prabhu
2017-04-10 15:39 ` Vlad Yasevich
2017-04-10 15:49 ` David Ahern
2017-04-15 1:51 ` Vlad Yasevich
2017-04-15 4:26 ` David Ahern
2017-04-18 7:52 ` Nicolas Dichtel
2017-04-09 1:36 ` Vlad Yasevich
2017-04-09 2:58 ` David Ahern
2017-04-07 21:25 ` [PATCH net-next 2/8] rtnetlink: Do not generate notification for UDP_TUNNEL_PUSH_INFO David Ahern
2017-04-07 21:25 ` [PATCH net-next 3/8] rtnetlink: Do not generate notifications for CHANGEADDR event David Ahern
2017-04-07 21:25 ` [PATCH net-next 4/8] rtnetlink: Do not generate notifications for POST_TYPE_CHANGE event David Ahern
2017-04-07 21:25 ` [PATCH net-next 5/8] rtnetlink: Remove NETDEV_CHANGEINFODATA netdev event David Ahern
2017-04-07 21:25 ` [PATCH net-next 6/8] rtnetlink: Do not generate notifications for PRECHANGEUPPER event David Ahern
2017-04-07 21:25 ` [PATCH net-next 7/8] rtnetlink: Do not generate notifications for NOTIFY_PEERS event David Ahern
2017-04-09 1:37 ` Vlad Yasevich [this message]
2017-04-07 21:25 ` [PATCH net-next 8/8] rtnetlink: Do not generate notifications for CHANGELOWERSTATE event 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=7a5c0cdd-7d9b-a8e9-a27c-591d165b5ab3@redhat.com \
--to=vyasevic@redhat.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
/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).