<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/net/bonding, branch linux-2.6.19.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.19.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.19.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-02-05T16:31:44Z</updated>
<entry>
<title>[PATCH] bonding: ARP monitoring broken on x86_64</title>
<updated>2007-02-05T16:31:44Z</updated>
<author>
<name>Andy Gospodarek</name>
</author>
<published>2007-01-29T20:08:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3002052b6358f932cbe381007ad20c76d5e4dca9'/>
<id>urn:sha1:3002052b6358f932cbe381007ad20c76d5e4dca9</id>
<content type='text'>
While working with the latest bonding code I noticed a nasty problem that
will prevent arp monitoring from always functioning correctly on x86_64
systems.  Comparing ints to longs and expecting reliable results on x86_64
is a bad idea.  With this patch, arp monitoring works correctly again.

Signed-off-by: Andy Gospodarek &lt;andy@greyhouse.net&gt;
Cc: "David S. Miller" &lt;davem@davemloft.net&gt;
Cc: Stephen Hemminger &lt;shemminger@osdl.org&gt;
Cc: Jeff Garzik &lt;jeff@garzik.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: incorrect bonding state reported via ioctl</title>
<updated>2007-01-10T19:05:17Z</updated>
<author>
<name>Andy Gospodarek</name>
</author>
<published>2006-11-21T16:46:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fae0ef93df6f6b3ebf9209d4be7112f97405814c'/>
<id>urn:sha1:fae0ef93df6f6b3ebf9209d4be7112f97405814c</id>
<content type='text'>
This is a small fix-up to finish out the work done by Jay Vosburgh to
add carrier-state support for bonding devices.  The output in
/proc/net/bonding/bondX was correct, but when collecting the same info
via an iotcl it could still be incorrect.

Signed-off-by: Andy Gospodarek &lt;andy@greyhouse.net&gt;
Cc: Jeff Garzik &lt;jeff@garzik.org&gt;
Cc: Stephen Hemminger &lt;shemminger@osdl.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: lockdep annotation</title>
<updated>2006-11-10T16:08:52Z</updated>
<author>
<name>Peter Zijlstra</name>
</author>
<published>2006-11-09T03:51:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0daa2303028a63dbd1b2e38f10854f0f7bf1ef9a'/>
<id>urn:sha1:0daa2303028a63dbd1b2e38f10854f0f7bf1ef9a</id>
<content type='text'>
=============================================
[ INFO: possible recursive locking detected ]
2.6.17-1.2600.fc6 #1

Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: fix deadlock on high loads in bond_alb_monitor()</title>
<updated>2006-10-05T11:01:25Z</updated>
<author>
<name>Karsten Keil</name>
</author>
<published>2006-09-30T06:28:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=39984a9fad0c642182f426d7771332d46f222103'/>
<id>urn:sha1:39984a9fad0c642182f426d7771332d46f222103</id>
<content type='text'>
In bond_alb_monitor the bond-&gt;curr_slave_lock write lock is taken
and then dev_set_promiscuity maybe called which can take some time,
depending on the network HW. If a network IRQ for this card come in
the softirq handler maybe try to deliver more packets which end up in
a request to the read lock of bond-&gt;curr_slave_lock -&gt; deadlock.
This issue was found by a test lab during network stress tests, this patch
disable the softirq handler for this case and solved the issue.

Signed-off-by: Karsten Keil &lt;kkeil@suse.de&gt;
Acked-by: Jay Vosburgh &lt;fubar@us.ibm.com&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
</content>
</entry>
<entry>
<title>[IPV4]: annotate struct in_ifaddr</title>
<updated>2006-09-29T01:00:55Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2006-09-29T01:00:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a144ea4b7a13087081ab5402fa9ad0bcfd249e67'/>
<id>urn:sha1:a144ea4b7a13087081ab5402fa9ad0bcfd249e67</id>
<content type='text'>
ifa_local, ifa_address, ifa_mask, ifa_broadcast and ifa_anycast are
net-endian.  Annotated them and variables that are inferred to be
net-endian.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: update version number</title>
<updated>2006-09-27T20:18:24Z</updated>
<author>
<name>Jay Vosburgh</name>
</author>
<published>2006-09-26T17:55:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0ba8821b12231386c8c1d506c682061f7225ae49'/>
<id>urn:sha1:0ba8821b12231386c8c1d506c682061f7225ae49</id>
<content type='text'>
	I neglected to properly update the version number in the recent
patch series; this sets it to something reasonable.

Signed-off-by: Jay Vosburgh &lt;fubar@us.ibm.com&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: Fix primary selection error at enslavement time</title>
<updated>2006-09-26T00:08:09Z</updated>
<author>
<name>Jay Vosburgh</name>
</author>
<published>2006-09-23T04:56:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8a8e447b2aa1f9139d0bfc94a2a3426be9c8d40a'/>
<id>urn:sha1:8a8e447b2aa1f9139d0bfc94a2a3426be9c8d40a</id>
<content type='text'>
	At enslavement time, the primary slave might not be activated if
there is already an active slave and the new slave is the primary.
Replaced complicated logic with a call to bond_select_active_slave(),
which does the right thing.

	Fixes http://bugzilla.kernel.org/show_bug.cgi?id=6378

Signed-off-by: Jay Vosburgh &lt;fubar@us.ibm.com&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: Don't mangle LACPDUs</title>
<updated>2006-09-26T00:08:09Z</updated>
<author>
<name>Jay Vosburgh</name>
</author>
<published>2006-09-23T04:55:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=89cc76f95af3608d83a1d70b3c76b71ffe66e1f7'/>
<id>urn:sha1:89cc76f95af3608d83a1d70b3c76b71ffe66e1f7</id>
<content type='text'>
	Fixed handling of 802.3ad LACPDUs.  Do not byte swap data in
place in the packet.  Updated nomenclature of "__ntohs_lacpdu" to be
"htons"; it was previously used for both ntohs and htons operations, but
only called ntohs functions.

Signed-off-by: Jay Vosburgh &lt;fubar@us.ibm.com&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: Validate probe replies in ARP monitor</title>
<updated>2006-09-26T00:08:09Z</updated>
<author>
<name>Jay Vosburgh</name>
</author>
<published>2006-09-23T04:54:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f5b2b966f032f22d3a289045a5afd4afa09f09c6'/>
<id>urn:sha1:f5b2b966f032f22d3a289045a5afd4afa09f09c6</id>
<content type='text'>
	Add logic to check ARP request / reply packets used for ARP
monitor link integrity checking.

	The current method simply examines the slave device to see if it
has sent and received traffic; this can be fooled by extraneous traffic.
For example, if multiple hosts running bonding are behind a common
switch, the probe traffic from the multiple instances of bonding will
update the tx/rx times on each other's slave devices.

Signed-off-by: Jay Vosburgh &lt;fubar@us.ibm.com&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: Don't release slaves when master is admin down</title>
<updated>2006-09-26T00:08:09Z</updated>
<author>
<name>jamal</name>
</author>
<published>2006-09-23T04:54:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=70298705bb29fb7982b85089adf17cd37b94baa7'/>
<id>urn:sha1:70298705bb29fb7982b85089adf17cd37b94baa7</id>
<content type='text'>
When a bonding netdevice is admin-ed down it loses the slaves
attributes (set via ifenslave). This is not consistent with other
behavior of netdevices (example a qdisc attached to a netdevice doesnt
disappear or an attached IP address etc).
The included patch fixes this. Ive tested by ifenslaving, downing the
bond, checking /proc and making sure it still has the slaves, up-ing the
bond and making sure things continue to work.

Jay/Bonding folks if you are ok with it, just ACK it or include it in
your tree etc. Otherwise we can discuss.

Acked-by: Jay Vosburgh &lt;fubar@us.ibm.com&gt;

Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
</content>
</entry>
</feed>
