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:51:46 +0000
From:	Rajesh Borundia <rajesh.borundia@...gic.com>
To:	Nikolay Aleksandrov <nikolay@...hat.com>,
	netdev <netdev@...r.kernel.org>
CC:	David Miller <davem@...emloft.net>,
	"agospoda@...hat.com" <agospoda@...hat.com>,
	Sony Chacko <sony.chacko@...gic.com>
Subject: RE: [PATCH net-next v3] netxen: write IP address to firmware when
 using bonding

-----Original Message-----
>From: Nikolay Aleksandrov [mailto:nikolay@...hat.com]
>Sent: Tuesday, March 12, 2013 6:19 PM
>To: netdev
>Cc: Rajesh Borundia; David Miller; agospoda@...hat.com; Sony Chacko
>Subject: [PATCH net-next v3] netxen: write IP address to firmware when
>using bonding
>
>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.
>
>V3: After testing and discussing this with Rajesh, I decided to keep the
>    vlan ip cache and just rename it to ip_cache since it will store
>bond
>    ip addresses too. A new master flag has been added to the ip cache
>to
>    denote that the address has been added because of a master device.
>    I've taken care of the enslave/release cases by checking for various
>    combinations of events and flags (e.g. netxen has a master, it's a
>    bond master and it's not marked as a slave means it is being
>enslaved
>    and is dev_open()ed in bond_enslave).
>    I've changed netxen_free_ip_list() to have a "master" parameter
>which
>    causes all IP addresses marked as master to be deleted (used when a
>    netxen is being released). I've made the patch use the new upper
>    device API as well. The following cases were tested:
>    - bond -> netxen
>    - vlan -> netxen
>    - vlan -> bond -> netxen

Acked-by : Rajesh Borundia <rajesh.borundia@...gic.com>


--
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