From: Vlad Yasevich <vyasevic@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: john.r.fastabend@intel.com, netdev@vger.kernel.org,
shemminger@vyatta.com, bridge@lists.linux-foundation.org,
jhs@mojatatu.com
Subject: Re: [PATCH 4/7] bridge: Automatically manage port promiscuous mode.
Date: Wed, 26 Feb 2014 11:02:17 -0500 [thread overview]
Message-ID: <530E1009.60605@redhat.com> (raw)
In-Reply-To: <20140226155111.GE15330@redhat.com>
On 02/26/2014 10:51 AM, Michael S. Tsirkin wrote:
> On Wed, Feb 26, 2014 at 10:18:22AM -0500, Vlad Yasevich wrote:
>> When there is only 1 flooding port, this port is programmed
>> with all the address
>
> all the addresses?
All statically configured ones plus locals.
Locals are needed preserve the bridge behavior of
being able to receive packets addresses to any of the
ports mac addresses on any interface.
This actually cuts the usability of this feature
in about half. :(
>
>> the bridge accumulated. This allows
>> us to place this port into non-promiscuous mode.
>> At other times, all ports are set as promiscuous. To help
>> track whether the bridge set the mode or not, a new
>> flag is introduced.
>>
>> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
>> ---
>> net/bridge/br_if.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++--
>> net/bridge/br_private.h | 1 +
>> 2 files changed, 47 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/bridge/br_if.c b/net/bridge/br_if.c
>> index e782c2e..51df642 100644
>> --- a/net/bridge/br_if.c
>> +++ b/net/bridge/br_if.c
>> @@ -136,7 +136,7 @@ static void del_nbp(struct net_bridge_port *p)
>>
>> sysfs_remove_link(br->ifobj, p->dev->name);
>>
>> - dev_set_promiscuity(dev, -1);
>> + dev_set_allmulti(dev, -1);
>>
>> spin_lock_bh(&br->lock);
>> br_stp_disable_port(p);
>> @@ -359,7 +359,7 @@ int br_add_if(struct net_bridge *br, struct net_device *dev)
>>
>> call_netdevice_notifiers(NETDEV_JOIN, dev);
>>
>> - err = dev_set_promiscuity(dev, 1);
>> + err = dev_set_allmulti(dev, 1);
>> if (err)
>> goto put_back;
>>
>> @@ -465,6 +465,48 @@ int br_del_if(struct net_bridge *br, struct net_device *dev)
>> return 0;
>> }
>>
>> +static int br_port_set_promisc(struct net_bridge_port *p)
>> +{
>> + int err = 0;
>> +
>> + if (p->flags & BR_PROMISC)
>> + return err;
>> +
>> + err = dev_set_promiscuity(p->dev, 1);
>> + if (err)
>> + return err;
>> +
>> + p->flags |= BR_PROMISC;
>> + return err;
>> +}
>> +
>
> you take pains to return an error code here,
> only to ignore it in the caller?
You are right. This can be turned to void.
>
>> +static void br_port_clear_promisc(struct net_bridge_port *p)
>> +{
>> + if (!(p->flags & BR_PROMISC))
>> + return;
>> +
>> + dev_set_promiscuity(p->dev, -1);
>> + p->flags &= ~BR_PROMISC;
>> +}
>> +
>> +/* When a port is added or removed or when the flooding status of
>> + * the port changes, this function is called to automatically mange
>> + * promiscuity setting of all the bridge ports. We are always called
>> + * under RTNL so can skip using rcu primitives.
>> + */
>> +static void br_manage_promisc(struct net_bridge *br)
>> +{
>> + struct net_bridge_port *p;
>> +
>> + list_for_each_entry(p, &br->port_list, list) {
>> + if (!br_port_exists(p->dev) ||
>> + (br->n_flood_ports == 1 && br->c_flood_port == p))
>> + br_port_clear_promisc(p);
>> + else
>> + br_port_set_promisc(p);
>> + }
>> +}
>> +
>> static void br_add_flood_port(struct net_bridge_port *p, struct net_bridge *br)
>> {
>> /* Increment the number of flooding ports, and if we
>> @@ -475,6 +517,7 @@ static void br_add_flood_port(struct net_bridge_port *p, struct net_bridge *br)
>> br->c_flood_port = p;
>>
>> br_fdb_addrs_sync(br);
>> + br_manage_promisc(br);
>> }
>>
>> static void br_del_flood_port(struct net_bridge_port *p, struct net_bridge *br)
>> @@ -502,6 +545,7 @@ static void br_del_flood_port(struct net_bridge_port *p, struct net_bridge *br)
>> }
>> }
>> }
>> + br_manage_promisc(br);
>> }
>>
>> void br_port_flags_change(struct net_bridge_port *p, unsigned long mask)
>> diff --git a/net/bridge/br_private.h b/net/bridge/br_private.h
>> index 40a6927..6670cb3 100644
>> --- a/net/bridge/br_private.h
>> +++ b/net/bridge/br_private.h
>> @@ -174,6 +174,7 @@ struct net_bridge_port
>> #define BR_ADMIN_COST 0x00000010
>> #define BR_LEARNING 0x00000020
>> #define BR_FLOOD 0x00000040
>> +#define BR_PROMISC 0x00000080
>>
>
> Considering you then have a separate logic in 7/7
> will this be cleaner as a per-port flag?
It is a per-port flag here. I can change it to
BR_PORT_PROMISC to make it clearer.
-vlad
>
>> #ifdef CONFIG_BRIDGE_IGMP_SNOOPING
>> struct bridge_mcast_query ip4_query;
>> --
>> 1.8.5.3
next prev parent reply other threads:[~2014-02-26 16:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 15:18 [PATCH RFC 0/7] Non-promisc bidge ports support Vlad Yasevich
2014-02-26 15:18 ` [PATCH 1/7] bridge: Turn flag change macro into a function Vlad Yasevich
2014-02-26 15:29 ` Michael S. Tsirkin
2014-02-26 15:36 ` Vlad Yasevich
2014-02-26 15:18 ` [PATCH 2/7] bridge: Keep track of ports capable of flooding Vlad Yasevich
2014-02-26 15:41 ` Michael S. Tsirkin
2014-02-26 15:41 ` Vlad Yasevich
2014-02-26 15:53 ` Michael S. Tsirkin
2014-02-27 11:59 ` Toshiaki Makita
2014-02-27 12:54 ` Vlad Yasevich
2014-02-26 15:18 ` [PATCH 3/7] bridge: Add addresses from static fdbs to bridge address list Vlad Yasevich
2014-02-26 15:46 ` Michael S. Tsirkin
2014-02-26 15:43 ` Vlad Yasevich
2014-02-26 16:23 ` Michael S. Tsirkin
2014-02-26 17:25 ` Vlad Yasevich
2014-02-26 17:33 ` Michael S. Tsirkin
2014-02-26 16:57 ` Stephen Hemminger
2014-02-26 17:35 ` Vlad Yasevich
2014-02-27 7:53 ` Michael S. Tsirkin
2014-02-27 13:08 ` Vlad Yasevich
2014-02-27 13:38 ` Michael S. Tsirkin
2014-02-26 15:18 ` [PATCH 4/7] bridge: Automatically manage port promiscuous mode Vlad Yasevich
2014-02-26 15:51 ` Michael S. Tsirkin
2014-02-26 16:02 ` Vlad Yasevich [this message]
2014-02-26 16:58 ` Stephen Hemminger
2014-02-26 17:32 ` Michael S. Tsirkin
2014-02-26 15:18 ` [PATCH 5/7] bridge: Correctly manage promiscuity when user requested it Vlad Yasevich
2014-02-26 15:18 ` [PATCH 6/7] bridge: Manage promisc mode when vlans are configured on top of a bridge Vlad Yasevich
2014-02-26 16:00 ` Michael S. Tsirkin
2014-02-26 16:05 ` Vlad Yasevich
2014-02-26 16:25 ` Michael S. Tsirkin
2014-02-27 12:06 ` Toshiaki Makita
2014-02-27 13:17 ` Vlad Yasevich
2014-02-28 19:34 ` Vlad Yasevich
2014-03-01 14:57 ` Toshiaki Makita
2014-03-03 12:12 ` Vlad Yasevich
2014-02-26 15:18 ` [PATCH 7/7] bridge: Support promisc management when all ports are non-flooding Vlad Yasevich
2014-02-26 15:57 ` Michael S. Tsirkin
2014-02-27 3:46 ` Vlad Yasevich
2014-02-27 7:29 ` Michael S. Tsirkin
2014-02-26 16:01 ` Michael S. Tsirkin
2014-02-26 16:34 ` [PATCH RFC 0/7] Non-promisc bidge ports support Michael S. Tsirkin
2014-02-26 23:59 ` Jamal Hadi Salim
2014-02-27 3:37 ` Vlad Yasevich
2014-02-27 8:54 ` [Bridge] " Amidu Sila
2014-02-27 7:20 ` Michael S. Tsirkin
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=530E1009.60605@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=jhs@mojatatu.com \
--cc=john.r.fastabend@intel.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).