Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: arkadis@mellanox.com
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
	bridge@lists.linux-foundation.org, idosch@mellanox.com,
	nikolay@cumulusnetworks.com
Subject: Re: [PATCH net-next v3] net: bridge: Fix improper taking over HW learned FDB
Date: Sun, 30 Apr 2017 22:46:52 -0400 (EDT)	[thread overview]
Message-ID: <20170430.224652.1616918504779575655.davem@davemloft.net> (raw)
In-Reply-To: <1493408347-44779-1-git-send-email-arkadis@mellanox.com>

From: Arkadi Sharshevsky <arkadis@mellanox.com>
Date: Fri, 28 Apr 2017 22:39:07 +0300

> Commit 7e26bf45e4cb ("net: bridge: allow SW learn to take over HW fdb
> entries") added the ability to "take over an entry which was previously
> learned via HW when it shows up from a SW port".
> 
> However, if an entry was learned via HW and then a control packet
> (e.g., ARP request) was trapped to the CPU, the bridge driver will
> update the entry and remove the externally learned flag, although the
> entry is still present in HW. Instead, only clear the externally learned
> flag in case of roaming.
> 
> Fixes: 7e26bf45e4cb ("net: bridge: allow SW learn to take over HW fdb entries")
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> Signed-off-by: Arkadi Sharashevsky <arkadis@mellanox.com>

Applied, thanks.

      parent reply	other threads:[~2017-05-01  2:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 19:39 [PATCH net-next v3] net: bridge: Fix improper taking over HW learned FDB Arkadi Sharshevsky
2017-04-28 21:33 ` Nikolay Aleksandrov
2017-05-01  2:46 ` David Miller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170430.224652.1616918504779575655.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=arkadis@mellanox.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=idosch@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox