[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <760db30a-859a-a365-e0f3-69a4433ef9bf@cumulusnetworks.com>
Date: Thu, 27 Apr 2017 13:59:38 -0600
From: David Ahern <dsa@...ulusnetworks.com>
To: vyasevic@...hat.com, Vladislav Yasevich <vyasevich@...il.com>,
netdev@...r.kernel.org
Cc: roopa <roopa@...ulusnetworks.com>, Jiri Pirko <jiri@...nulli.us>
Subject: Re: [PATCH net-next V3 2/2] rtnl: Add support for netdev event
attribute to link messages
On 4/27/17 1:43 PM, Vlad Yasevich wrote:
>> For example, NETDEV_CHANGEINFODATA is only for bonds though nothing
>> about the name suggests it is a bonding notification. This one was added
>> specifically to notify userspace (d4261e5650004), yet seems to happen
>> only during a changelink and that already generates a RTM_NEWLINK
>> message via do_setlink. Since the rtnetlink_event message does not
>> contain anything "NETDEV_CHANGEINFODATA" related what purpose does it
>> really serve besides duplicating netlink messages to userspace.
>>
>
> I am not sure about this one, but if you have an app trying to monitor
> for this event, it can't really since there is no info in the netlink message.
I cc'ed Jiri on this thread hoping he would explain the intent.
I propose it gets removed.
Powered by blists - more mailing lists