mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Elliot Ayrey <Elliot.Ayrey@alliedtelesis.co.nz>
To: "andrew@lunn.ch" <andrew@lunn.ch>,
	"olteanv@gmail.com" <olteanv@gmail.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"razor@blackwall.org" <razor@blackwall.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"roopa@nvidia.com" <roopa@nvidia.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"horms@kernel.org" <horms@kernel.org>,
	"kuba@kernel.org" <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bridge@lists.linux.dev" <bridge@lists.linux.dev>
Subject: Re: [RFC net-next (resend) 1/4] net: bridge: respect sticky flag on external learn
Date: Sun, 24 Nov 2024 21:01:46 +0000	[thread overview]
Message-ID: <f2ac33e7b8ec0fefa48fe7cd3b1004abab67dcb1.camel@alliedtelesis.co.nz> (raw)
In-Reply-To: <20241108035546.2055996-2-elliot.ayrey@alliedtelesis.co.nz>

On Sat, 2024-11-09 at 15:32 +0200, Nikolay Aleksandrov wrote:
> So you have a sticky fdb entry added, but it is still allowed to roam
> in HW?

No the hardware has informed us a host has _tried_ to roam.

As I think about this more, using the sticky bit alone probably isn't
the best idea and it might be better if this mechanism were related to
a port being locked? After all the port being locked in hardware is
what generates this event.

  reply	other threads:[~2024-11-24 21:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  3:55 [RFC net-next (resend) 0/4] Send notifications for roaming hosts Elliot Ayrey
2024-11-08  3:55 ` [RFC net-next (resend) 1/4] net: bridge: respect sticky flag on external learn Elliot Ayrey
2024-11-24 21:01   ` Elliot Ayrey [this message]
2024-11-24 22:01     ` Nikolay Aleksandrov
2024-11-08  3:55 ` [RFC net-next (resend) 2/4] net: bridge: send notification for roaming hosts Elliot Ayrey
2024-11-08 13:42   ` Andrew Lunn
2024-11-24 21:32     ` Elliot Ayrey
2024-11-24 21:23   ` Elliot Ayrey
2024-11-24 21:39     ` Andrew Lunn
2024-11-24 21:57     ` Nikolay Aleksandrov
2024-11-08  3:55 ` [RFC net-next (resend) 3/4] net: dsa: mv88e6xxx: handle member-violations Elliot Ayrey
2024-11-08 13:49   ` Andrew Lunn
2024-11-11  4:39     ` Elliot Ayrey
2024-11-08  3:55 ` [RFC net-next (resend) 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=f2ac33e7b8ec0fefa48fe7cd3b1004abab67dcb1.camel@alliedtelesis.co.nz \
    --to=elliot.ayrey@alliedtelesis.co.nz \
    --cc=andrew@lunn.ch \
    --cc=bridge@lists.linux.dev \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®