From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: [net-next v3] bridge: trigger RTM_NEWLINK when interface is modified by bridge ioctl Date: Thu, 21 Sep 2017 11:29:55 -0600 Message-ID: <4bd6834a-899a-b136-9886-249dadd5a6a6@gmail.com> References: <20170920162140.369bb198@xeon-e3> <20170921100525.20395-1-vincent@bernat.im> <0cdf06b9-e67d-c035-e0f1-c4eb143bf631@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: "netdev@vger.kernel.org" , bridge@lists.linux-foundation.org, Vincent Bernat , David Miller To: Roopa Prabhu , David Ahern Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: bridge-bounces@lists.linux-foundation.org Errors-To: bridge-bounces@lists.linux-foundation.org List-Id: netdev.vger.kernel.org On 9/21/17 11:20 AM, Roopa Prabhu wrote: > this patch seems fine...but ideally I would have assumed > netdev_upper_dev_unlink which > is eventually called in both paths would generate the RTN_NEWLINK > IFF_MASTER in response > to the NETDEV_CHANGEUPPER notifier. If we add it there now, it might > need some more fixes > to not generate redundant notifications for the netlink case. Agreed and it is another pandora's box