[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170527.185210.1614681423458551500.davem@davemloft.net>
Date: Sat, 27 May 2017 18:52:10 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: vyasevich@...il.com
Cc: netdev@...r.kernel.org, dsahern@...il.com,
roopa@...ulusnetworks.com, jiri@...nulli.us, vfalico@...il.com,
andy@...yhouse.net, vyasevic@...hat.com
Subject: Re: [PATCH V6 net-next 0/2] rtnetlink: Updates to
rtnetlink_event()
From: Vladislav Yasevich <vyasevich@...il.com>
Date: Sat, 27 May 2017 10:14:33 -0400
> First is the patch to add IFLA_EVENT attribute to the netlink message. It
> supports only currently white-listed events.
> Like before, this is just an attribute that gets added to the rtnetlink
> message only when the messaged was generated as a result of a netdev event.
> In my case, this is necessary since I want to trap NETDEV_NOTIFY_PEERS
> event (also possibly NETDEV_RESEND_IGMP event) and perform certain actions
> in user space. This is not possible since the messages generated as
> a result of netdev events do not usually contain any changed data. They
> are just notifications. This patch exposes this notification type to
> userspace.
>
> Second, I remove duplicate messages that a result of a change to bonding
> options. If netlink is used to configure bonding options, 2 messages
> are generated, one as a result NETDEV_CHANGEINFODATA event triggered by
> bonding code and one a result of device state changes triggered by
> netdev_state_change (called from do_setlink).
...
Series applied, thanks Vlad.
Powered by blists - more mailing lists