From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Subject: Re: [PATCH net-next] bridge: add notification over netlink when STP changes state Date: Wed, 18 May 2011 08:19:40 -0700 Message-ID: <4DD3E38C.30609@candelatech.com> References: <20110518081718.0b1fc390@nehalam> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Miller , bridge@linux-foundation.org, netdev@vger.kernel.org To: Stephen Hemminger Return-path: Received: from mail.candelatech.com ([208.74.158.172]:41713 "EHLO ns3.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933164Ab1ERPTq (ORCPT ); Wed, 18 May 2011 11:19:46 -0400 In-Reply-To: <20110518081718.0b1fc390@nehalam> Sender: netdev-owner@vger.kernel.org List-ID: On 05/18/2011 08:17 AM, Stephen Hemminger wrote: > The first netlink code in the bridge module was to notify > user space implementations of Spanning Tree Protocol about > new ports. It did not handle the case of kernel mode STP > changing states which could be useful for monitoring. > > This patch causes RTM_NEWLINK message to occur on kernel > transitions. It does not send message if request was from user > space STP, since that would cause reflection and break existing > API. So one app monitoring the system won't get updates if another app makes changes? Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com