netdev - Re: [PATCH net-next v3] netxen: write IP address to firmware when using bonding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Mar 2013 11:34:23 +0100
From:	Nikolay Aleksandrov <nikolay@...hat.com>
To:	David Miller <davem@...emloft.net>
CC:	netdev@...r.kernel.org, rajesh.borundia@...gic.com,
	agospoda@...hat.com, sony.chacko@...gic.com
Subject: Re: [PATCH net-next v3] netxen: write IP address to firmware when
 using bonding

On 13/03/13 09:42, David Miller wrote:
> From: Nikolay Aleksandrov <nikolay@...hat.com>
> Date: Tue, 12 Mar 2013 13:49:01 +0100
> 
>> This patch allows LRO aggregation on bonded devices that contain an
>> NX3031 device. It also adds a for_each_netdev_in_bond_rcu(bond, slave)
>> macro which executes for each slave that has bond as master.
> 
> The new logic looks like it will configure the IPs for bonding
> but not for VLANs, is that intentional?
The case bond -> vlan -> netxen was intentionally dropped as it leads to
many new issues, if that is what you are referring to. The case vlan ->
netxen still works, since the address of orig_dev is unconditionally
programmed if the original dev is a netxen. The problem was with a bond
acting on a vlan which is configured on a netxen because we would have
to keep track of which bonding master the programmed addresses belong to.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html