[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150524.225902.2017701461230237731.davem@davemloft.net>
Date: Sun, 24 May 2015 22:59:02 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: nikolay@...ulusnetworks.com
Cc: netdev@...r.kernel.org, wkok@...ulusnetworks.com,
stephen@...workplumber.org, bridge@...ts.linux-foundation.org
Subject: Re: [PATCH net-next] bridge: skip fdb add if the port shouldn't
learn
From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Date: Thu, 21 May 2015 03:42:57 -0700
> From: Wilson Kok <wkok@...ulusnetworks.com>
>
> Check in fdb_add_entry() if the source port should learn, similar
> check is used in br_fdb_update.
> Note that new fdb entries which are added manually or
> as local ones are still permitted.
> This patch has been tested by running traffic via a bridge port and
> switching the port's state, also by manually adding/removing entries
> from the bridge's fdb.
>
> Signed-off-by: Wilson Kok <wkok@...ulusnetworks.com>
> Signed-off-by: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
> ---
> Nik: Maybe it'd be better if we returned an error even though it
> doesn't look necessary. I'm open to suggestions.
If you don't return an error, then rtnetlink.c is going to emit a
NEWNEIGH netlink message. I seriously doubt we want that to happen.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists