From: Nikolay Aleksandrov <nikolay@nvidia.com>
To: Hans Schultz <schultz.hans@gmail.com>, <davem@davemloft.net>,
<kuba@kernel.org>
Cc: <netdev@vger.kernel.org>,
Hans Schultz <schultz.hans+netdev@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Roopa Prabhu <roopa@nvidia.com>, Shuah Khan <shuah@kernel.org>,
"Stephen Suryaputra" <ssuryaextr@gmail.com>,
David Ahern <dsahern@kernel.org>,
"Ido Schimmel" <idosch@nvidia.com>,
Petr Machata <petrm@nvidia.com>, Amit Cohen <amcohen@nvidia.com>,
Po-Hsu Lin <po-hsu.lin@canonical.com>,
Baowen Zheng <baowen.zheng@corigine.com>,
<linux-kernel@vger.kernel.org>,
<bridge@lists.linux-foundation.org>,
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH net-next v3 1/5] net: bridge: Add support for bridge port in locked mode
Date: Sat, 19 Feb 2022 11:46:37 +0200 [thread overview]
Message-ID: <60f020b7-53b8-4f3c-ead2-8077aad8e5bb@nvidia.com> (raw)
In-Reply-To: <20220218155148.2329797-2-schultz.hans+netdev@gmail.com>
On 18/02/2022 17:51, Hans Schultz wrote:
> In a 802.1X scenario, clients connected to a bridge port shall not
> be allowed to have traffic forwarded until fully authenticated.
> A static fdb entry of the clients MAC address for the bridge port
> unlocks the client and allows bidirectional communication.
>
> This scenario is facilitated with setting the bridge port in locked
> mode, which is also supported by various switchcore chipsets.
>
> Signed-off-by: Hans Schultz <schultz.hans+netdev@gmail.com>
> ---
> include/linux/if_bridge.h | 1 +
> include/uapi/linux/if_link.h | 1 +
> net/bridge/br_input.c | 10 +++++++++-
> net/bridge/br_netlink.c | 6 +++++-
> 4 files changed, 16 insertions(+), 2 deletions(-)
>
Hi Hans,
The patch looks good overall, I have one minor cosmetic comment below.
> diff --git a/include/linux/if_bridge.h b/include/linux/if_bridge.h
> index 509e18c7e740..3aae023a9353 100644
> --- a/include/linux/if_bridge.h
> +++ b/include/linux/if_bridge.h
> @@ -58,6 +58,7 @@ struct br_ip_list {
> #define BR_MRP_LOST_CONT BIT(18)
> #define BR_MRP_LOST_IN_CONT BIT(19)
> #define BR_TX_FWD_OFFLOAD BIT(20)
> +#define BR_PORT_LOCKED BIT(21)
>
> #define BR_DEFAULT_AGEING_TIME (300 * HZ)
>
> diff --git a/include/uapi/linux/if_link.h b/include/uapi/linux/if_link.h
> index 6218f93f5c1a..a45cc0a1f415 100644
> --- a/include/uapi/linux/if_link.h
> +++ b/include/uapi/linux/if_link.h
> @@ -537,6 +537,7 @@ enum {
> IFLA_BRPORT_MRP_IN_OPEN,
> IFLA_BRPORT_MCAST_EHT_HOSTS_LIMIT,
> IFLA_BRPORT_MCAST_EHT_HOSTS_CNT,
> + IFLA_BRPORT_LOCKED,
> __IFLA_BRPORT_MAX
> };
> #define IFLA_BRPORT_MAX (__IFLA_BRPORT_MAX - 1)
> diff --git a/net/bridge/br_input.c b/net/bridge/br_input.c
> index b50382f957c1..e99f635ff727 100644
> --- a/net/bridge/br_input.c
> +++ b/net/bridge/br_input.c
> @@ -81,6 +81,7 @@ int br_handle_frame_finish(struct net *net, struct sock *sk, struct sk_buff *skb
> if (!p || p->state == BR_STATE_DISABLED)
> goto drop;
>
> + br = p->br;
> brmctx = &p->br->multicast_ctx;
> pmctx = &p->multicast_ctx;
> state = p->state;
> @@ -88,10 +89,17 @@ int br_handle_frame_finish(struct net *net, struct sock *sk, struct sk_buff *skb
> &state, &vlan))
> goto out;
>
> + if (p->flags & BR_PORT_LOCKED) {
> + struct net_bridge_fdb_entry *fdb_src =
> + br_fdb_find_rcu(br, eth_hdr(skb)->h_source, vid);
Please leave an empty line between variable declaration and the code.
> + if (!fdb_src || READ_ONCE(fdb_src->dst) != p ||
> + test_bit(BR_FDB_LOCAL, &fdb_src->flags))
> + goto drop;
> + }
> +
With the above change you can add my Acked-by tag.
Thanks,
Nik
next prev parent reply other threads:[~2022-02-19 9:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 15:51 [PATCH net-next v3 0/5] Add support for locked bridge ports (for 802.1X) Hans Schultz
2022-02-18 15:51 ` [PATCH net-next v3 1/5] net: bridge: Add support for bridge port in locked mode Hans Schultz
2022-02-19 9:46 ` Nikolay Aleksandrov [this message]
2022-02-20 9:18 ` Ido Schimmel
2022-02-18 15:51 ` [PATCH net-next v3 2/5] net: bridge: Add support for offloading of locked port flag Hans Schultz
2022-02-19 9:47 ` Nikolay Aleksandrov
2022-02-20 9:19 ` Ido Schimmel
2022-02-18 15:51 ` [PATCH net-next v3 3/5] net: dsa: Add support for offloaded " Hans Schultz
2022-02-19 9:56 ` Vladimir Oltean
2022-02-18 15:51 ` [PATCH net-next v3 4/5] net: dsa: mv88e6xxx: Add support for bridge port locked mode Hans Schultz
2022-02-19 10:00 ` Vladimir Oltean
2022-02-20 9:21 ` Ido Schimmel
2022-02-21 14:05 ` Hans Schultz
2022-02-18 15:51 ` [PATCH net-next v3 5/5] selftests: forwarding: tests of locked port feature Hans Schultz
2022-02-18 21:02 ` Shuah Khan
2022-02-19 9:48 ` Nikolay Aleksandrov
2022-02-20 9:12 ` Ido Schimmel
2022-02-21 9:20 ` Hans Schultz
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=60f020b7-53b8-4f3c-ead2-8077aad8e5bb@nvidia.com \
--to=nikolay@nvidia.com \
--cc=amcohen@nvidia.com \
--cc=andrew@lunn.ch \
--cc=baowen.zheng@corigine.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=petrm@nvidia.com \
--cc=po-hsu.lin@canonical.com \
--cc=roopa@nvidia.com \
--cc=schultz.hans+netdev@gmail.com \
--cc=schultz.hans@gmail.com \
--cc=shuah@kernel.org \
--cc=ssuryaextr@gmail.com \
--cc=vivien.didelot@gmail.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