netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH net-next,v2 4/9] bridge: resolve forwarding path for bridge devices
Date: Thu, 22 Oct 2020 13:24:21 +0300	[thread overview]
Message-ID: <a0d79083b43d212351d56718a0ec40d8e9b4888b.camel@blackwall.org> (raw)
In-Reply-To: <20201015163038.26992-5-pablo@netfilter.org>

On Thu, 2020-10-15 at 18:30 +0200, Pablo Neira Ayuso wrote:
> Add .ndo_fill_forward_path for bridge devices.
> 
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> v2: no changes
> 
>  include/linux/netdevice.h |  1 +
>  net/bridge/br_device.c    | 22 ++++++++++++++++++++++
>  2 files changed, 23 insertions(+)
> 
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index d4263ed5dd79..4cabdbc672d3 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -836,6 +836,7 @@ typedef u16 (*select_queue_fallback_t)(struct net_device *dev,
>  enum net_device_path_type {
>  	DEV_PATH_ETHERNET = 0,
>  	DEV_PATH_VLAN,
> +	DEV_PATH_BRIDGE,
>  };
>  
>  struct net_device_path {
> diff --git a/net/bridge/br_device.c b/net/bridge/br_device.c
> index 6f742fee874a..06046a35868d 100644
> --- a/net/bridge/br_device.c
> +++ b/net/bridge/br_device.c
> @@ -391,6 +391,27 @@ static int br_del_slave(struct net_device *dev, struct net_device *slave_dev)
>  	return br_del_if(br, slave_dev);
>  }
>  
> +static int br_fill_forward_path(struct net_device_path_ctx *ctx,
> +				struct net_device_path *path)
> +{
> +	struct net_bridge_fdb_entry *f;
> +	struct net_bridge *br;
> +
> +	if (netif_is_bridge_port(ctx->dev))
> +		return -1;
> +
> +	br = netdev_priv(ctx->dev);
> +	f = br_fdb_find_rcu(br, ctx->daddr, 0);
> +	if (!f || !f->dst)
> +		return -1;
> +
> +	path->type = DEV_PATH_BRIDGE;
> +	path->dev = f->dst->br->dev;
> +	ctx->dev = f->dst->dev;

Please use READ_ONCE() for f->dst since it can become NULL if the entry
is changed to point to the bridge device itself after the check above. I've had
a patch in my queue that changes the bridge to use WRITE_ONCE() to annotate it
as a lockless read.

Thanks,
 Nik

> +
> +	return 0;
> +}
> +
>  static const struct ethtool_ops br_ethtool_ops = {
>  	.get_drvinfo		 = br_getinfo,
>  	.get_link		 = ethtool_op_get_link,
> @@ -425,6 +446,7 @@ static const struct net_device_ops br_netdev_ops = {
>  	.ndo_bridge_setlink	 = br_setlink,
>  	.ndo_bridge_dellink	 = br_dellink,
>  	.ndo_features_check	 = passthru_features_check,
> +	.ndo_fill_forward_path	 = br_fill_forward_path,
>  };
>  
>  static struct device_type br_type = {



  reply	other threads:[~2020-10-22 10:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 16:30 [PATCH net-next,v2 0/9] netfilter: flowtable bridge and vlan enhancements Pablo Neira Ayuso
2020-10-15 16:30 ` [PATCH net-next,v2 1/9] netfilter: flowtable: add xmit path types Pablo Neira Ayuso
2020-10-15 16:30 ` [PATCH net-next,v2 2/9] net: resolve forwarding path from virtual netdevice and HW destination address Pablo Neira Ayuso
2020-10-15 16:30 ` [PATCH net-next,v2 3/9] net: 8021q: resolve forwarding path for vlan devices Pablo Neira Ayuso
2020-10-15 16:30 ` [PATCH net-next,v2 4/9] bridge: resolve forwarding path for bridge devices Pablo Neira Ayuso
2020-10-22 10:24   ` Nikolay Aleksandrov [this message]
2020-10-15 16:30 ` [PATCH net-next,v2 5/9] netfilter: flowtable: use dev_fill_forward_path() to obtain ingress device Pablo Neira Ayuso
2020-10-15 16:30 ` [PATCH net-next,v2 6/9] netfilter: flowtable: use dev_fill_forward_path() to obtain egress device Pablo Neira Ayuso
2020-10-19  9:32   ` Jeremy Sowden
2020-10-15 16:30 ` [PATCH net-next,v2 7/9] netfilter: flowtable: add direct xmit path Pablo Neira Ayuso
2020-10-15 16:30 ` [PATCH net-next,v2 8/9] netfilter: flowtable: bridge port support Pablo Neira Ayuso
2020-10-19  9:32   ` Jeremy Sowden
2020-10-15 16:30 ` [PATCH net-next,v2 9/9] netfilter: flowtable: add vlan support Pablo Neira Ayuso
2020-10-15 19:47 ` [PATCH net-next,v2 0/9] netfilter: flowtable bridge and vlan enhancements Jakub Kicinski
2020-10-15 23:04   ` Pablo Neira Ayuso

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=a0d79083b43d212351d56718a0ec40d8e9b4888b.camel@blackwall.org \
    --to=razor@blackwall.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).