From: Nikolay Aleksandrov <razor@blackwall.org>
To: Elliot Ayrey <elliot.ayrey@alliedtelesis.co.nz>
Cc: davem@davemloft.net, Roopa Prabhu <roopa@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
bridge@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next 1/4] net: bridge: respect sticky flag on external learn
Date: Sat, 9 Nov 2024 15:32:05 +0200 [thread overview]
Message-ID: <Zy9kVceo3w-YRA8S@penguin> (raw)
In-Reply-To: <20241108032422.2011802-2-elliot.ayrey@alliedtelesis.co.nz>
On Fri, Nov 08, 2024 at 04:24:18PM +1300, Elliot Ayrey wrote:
> The fdb sticky flag is used to stop a host from roaming to another
> port. However upon receiving a switchdev notification to update an fdb
> entry the sticky flag is not respected and as long as the new entry is
> not locked the host will be allowed to roam to the new port.
>
> Fix this by considering the sticky flag before allowing an externally
> learned host to roam.
>
> Signed-off-by: Elliot Ayrey <elliot.ayrey@alliedtelesis.co.nz>
> ---
> net/bridge/br_fdb.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
So you have a sticky fdb entry added, but it is still allowed to roam in HW?
> diff --git a/net/bridge/br_fdb.c b/net/bridge/br_fdb.c
> index 1cd7bade9b3b..d0eeedc03390 100644
> --- a/net/bridge/br_fdb.c
> +++ b/net/bridge/br_fdb.c
> @@ -1457,7 +1457,8 @@ int br_fdb_external_learn_add(struct net_bridge *br, struct net_bridge_port *p,
>
> fdb->updated = jiffies;
>
> - if (READ_ONCE(fdb->dst) != p) {
> + if (READ_ONCE(fdb->dst) != p &&
> + !test_bit(BR_FDB_STICK, &fdb->flags)) {
> WRITE_ONCE(fdb->dst, p);
> modified = true;
> }
next prev parent reply other threads:[~2024-11-09 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241108032422.2011802-1-elliot.ayrey@alliedtelesis.co.nz>
2024-11-08 3:24 ` [RFC net-next 1/4] net: bridge: respect sticky flag on external learn Elliot Ayrey
2024-11-09 13:32 ` Nikolay Aleksandrov [this message]
2024-11-08 3:24 ` [RFC net-next 2/4] net: bridge: send notification for roaming hosts Elliot Ayrey
2024-11-09 13:40 ` Nikolay Aleksandrov
2024-11-08 3:24 ` [RFC net-next 3/4] net: dsa: mv88e6xxx: handle member-violations Elliot Ayrey
2024-11-08 3:24 ` [RFC net-next 4/4] net: dsa: mv88e6xxx: cache fid-to-vid association Elliot Ayrey
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=Zy9kVceo3w-YRA8S@penguin \
--to=razor@blackwall.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elliot.ayrey@alliedtelesis.co.nz \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roopa@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.