[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56E96A3B.1030907@cumulusnetworks.com>
Date: Wed, 16 Mar 2016 15:14:19 +0100
From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
To: Xin Long <lucien.xin@...il.com>,
network dev <netdev@...r.kernel.org>
Cc: davem@...emloft.net,
Hannes Frederic Sowa <hannes@...essinduktion.org>
Subject: Re: [PATCH net-next 4/6] bridge: a netlink notification should be
sent when those attributes are changed by br_sysfs_br
On 03/16/2016 02:34 PM, Xin Long wrote:
> Now when we change the attributes of bridge or br_port by netlink,
> a relevant netlink notification will be sent, but if we change them
> by ioctl or sysfs, no notification will be sent.
>
> We should ensure that whenever those attributes change internally or from
> sysfs/ioctl, that a netlink notification is sent out to listeners.
>
> Also, NetworkManager will use this in the future to listen for out-of-band
> bridge master attribute updates and incorporate them into the runtime
> configuration.
>
> This patch is used for br_sysfs_br. and we also need to remove some
> rtnl_trylock in old functions so that we can call it in a common one.
>
> Signed-off-by: Xin Long <lucien.xin@...il.com>
> ---
> net/bridge/br_sysfs_br.c | 17 ++++++++---------
> net/bridge/br_vlan.c | 30 +++++-------------------------
> 2 files changed, 13 insertions(+), 34 deletions(-)
>
What about the group_addr option ? Changing it will not generate a notification.
Powered by blists - more mailing lists