From: netdev@kapio-technology.com
To: Vladimir Oltean <olteanv@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 net-next 3/3] net: dsa: mv88e6xxx: mac-auth/MAB implementation
Date: Sat, 07 Jan 2023 11:32:06 +0100 [thread overview]
Message-ID: <6abb27f946d39602bd05cdcbea21766c@kapio-technology.com> (raw)
In-Reply-To: <20230106164112.qwpqszvrmb5uv437@skbuf>
On 2023-01-06 17:41, Vladimir Oltean wrote:
> On Fri, Jan 06, 2023 at 05:05:29PM +0100, Hans J. Schultz wrote:
>> This implementation for the Marvell mv88e6xxx chip series is based on
>> handling ATU miss violations occurring when packets ingress on a port
>> that is locked with learning on. This will trigger a
>> SWITCHDEV_FDB_ADD_TO_BRIDGE event, which will result in the bridge
>> module
>> adding a locked FDB entry. This bridge FDB entry will not age out as
>> it has the extern_learn flag set.
>>
>> Userspace daemons can listen to these events and either accept or deny
>> access for the host, by either replacing the locked FDB entry with a
>> simple entry or leave the locked entry.
>>
>> If the host MAC address is already present on another port, a ATU
>> member violation will occur, but to no real effect, and the packet
>> will
>> be dropped in hardware. Statistics on these violations can be shown
>> with
>> the command and example output of interest:
>>
>> ethtool -S ethX
>> NIC statistics:
>> ...
>> atu_member_violation: 5
>> atu_miss_violation: 23
>> ...
>>
>> Where ethX is the interface of the MAB enabled port.
>>
>> Furthermore, as added vlan interfaces where the vid is not added to
>> the
>> VTU will cause ATU miss violations reporting the FID as
>> MV88E6XXX_FID_STANDALONE, we need to check and skip the miss
>> violations
>> handling in this case.
>>
>> Signed-off-by: Hans J. Schultz <netdev@kapio-technology.com>
>> ---
>
> Please add Acked-by/Reviewed-by tags when posting new versions.
> However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
>
> If a tag was not added on purpose, please state why and what changed.
>
> Missing tags:
>
> Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
>
>
> Please allow at least 24 hours between patch submissions to give time
> for other review comments.
I presume that since I move the exit tag 'out' to this patch, it has
changed and the review tag is reset?
next prev parent reply other threads:[~2023-01-07 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:05 [PATCH v3 net-next 0/3] mv88e6xxx: Add MAB offload support Hans J. Schultz
2023-01-06 16:05 ` [PATCH v3 net-next 1/3] net: dsa: mv88e6xxx: change default return of mv88e6xxx_port_bridge_flags Hans J. Schultz
2023-01-06 16:39 ` Vladimir Oltean
2023-01-06 16:05 ` [PATCH v3 net-next 2/3] net: dsa: mv88e6xxx: shorten the locked section in mv88e6xxx_g1_atu_prob_irq_thread_fn() Hans J. Schultz
2023-01-06 16:37 ` Vladimir Oltean
2023-01-07 9:44 ` netdev
2023-01-07 11:40 ` Vladimir Oltean
2023-01-06 16:05 ` [PATCH v3 net-next 3/3] net: dsa: mv88e6xxx: mac-auth/MAB implementation Hans J. Schultz
2023-01-06 16:41 ` Vladimir Oltean
2023-01-07 10:32 ` netdev [this message]
2023-01-07 11:37 ` Vladimir Oltean
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=6abb27f946d39602bd05cdcbea21766c@kapio-technology.com \
--to=netdev@kapio-technology.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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®