<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net, branch v2.6.17.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/net?h=v2.6.17.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/net?h=v2.6.17.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2006-06-30T00:17:16Z</updated>
<entry>
<title>[PATCH] IPV6 ADDRCONF: Fix default source address selection without CONFIG_IPV6_PRIVACY</title>
<updated>2006-06-30T00:17:16Z</updated>
<author>
<name>YOSHIFUJI Hideaki</name>
<email>yoshfuji@linux-ipv6.org</email>
</author>
<published>2006-06-22T08:42:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e778d0ec93ec97fb851b8e0bd5e1488f083baa6a'/>
<id>urn:sha1:e778d0ec93ec97fb851b8e0bd5e1488f083baa6a</id>
<content type='text'>
We need to update hiscore.rule even if we don't enable CONFIG_IPV6_PRIVACY,
because we have more less significant rule; longest match.

Signed-off-by: YOSHIFUJI Hideaki &lt;yoshfuji@linux-ipv6.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] IPV6: Fix source address selection.</title>
<updated>2006-06-30T00:17:16Z</updated>
<author>
<name>Łukasz Stelmach</name>
<email>stlman@poczta.fm</email>
</author>
<published>2006-06-22T08:39:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ac16ac4c1202baff72f889f3904ca480bea93d76'/>
<id>urn:sha1:ac16ac4c1202baff72f889f3904ca480bea93d76</id>
<content type='text'>
Two additional labels (RFC 3484, sec. 10.3) for IPv6 addreses
are defined to make a distinction between global unicast
addresses and Unique Local Addresses (fc00::/7, RFC 4193) and
Teredo (2001::/32, RFC 4380). It is necessary to avoid attempts
of connection that would either fail (eg. fec0:: to 2001:feed::)
or be sub-optimal (2001:0:: to 2001:feed::).

Signed-off-by: Łukasz Stelmach &lt;stlman@poczta.fm&gt;
Signed-off-by: YOSHIFUJI Hideaki &lt;yoshfuji@linux-ipv6.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] ETHTOOL: Fix UFO typo</title>
<updated>2006-06-30T00:17:15Z</updated>
<author>
<name>Herbert Xu</name>
<email>herbert@gondor.apana.org.au</email>
</author>
<published>2006-06-20T07:09:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=94f37cf0a304c16dcf86ec542e88b5448b2edfb7'/>
<id>urn:sha1:94f37cf0a304c16dcf86ec542e88b5448b2edfb7</id>
<content type='text'>
The function ethtool_get_ufo was referring to ETHTOOL_GTSO instead of
ETHTOOL_GUFO.

Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] SCTP: Fix persistent slowdown in sctp when a gap ack consumes rx buffer.</title>
<updated>2006-06-30T00:17:15Z</updated>
<author>
<name>Neil Horman</name>
<email>nhorman@tuxdriver.com</email>
</author>
<published>2006-06-20T07:09:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c2ba44b229b04cbd57106107d0047e2c666040ce'/>
<id>urn:sha1:c2ba44b229b04cbd57106107d0047e2c666040ce</id>
<content type='text'>
In the event that our entire receive buffer is full with a series of
chunks that represent a single gap-ack, and then we accept a chunk
(or chunks) that fill in the gap between the ctsn and the first gap,
we renege chunks from the end of the buffer, which effectively does
nothing but move our gap to the end of our received tsn stream. This
does little but move our missing tsns down stream a little, and, if the
sender is sending sufficiently large retransmit frames, the result is a
perpetual slowdown which can never be recovered from, since the only
chunk that can be accepted to allow progress in the tsn stream necessitates
that a new gap be created to make room for it. This leads to a constant
need for retransmits, and subsequent receiver stalls. The fix I've come up
with is to deliver the frame without reneging if we have a full receive
buffer and the receiving sockets sk_receive_queue is empty(indicating that
the receive buffer is being blocked by a missing tsn).

Signed-off-by: Neil Horman &lt;nhorman@tuxdriver.com&gt;
Signed-off-by: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] SCTP: Send only 1 window update SACK per message.</title>
<updated>2006-06-30T00:17:15Z</updated>
<author>
<name>Tsutomu Fujii</name>
<email>t-fujii@nb.jp.nec.com</email>
</author>
<published>2006-06-20T07:08:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f0a0819784268d7ca479b4538b07124249137500'/>
<id>urn:sha1:f0a0819784268d7ca479b4538b07124249137500</id>
<content type='text'>
Right now, every time we increase our rwnd by more then MTU bytes, we
trigger a SACK.  When processing large messages, this will generate a
SACK for almost every other SCTP fragment. However since we are freeing
the entire message at the same time, we might as well collapse the SACK
generation to 1.

Signed-off-by: Tsutomu Fujii &lt;t-fujii@nb.jp.nec.com&gt;
Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] SCTP: Reset rtt_in_progress for the chunk when processing its sack.</title>
<updated>2006-06-30T00:17:15Z</updated>
<author>
<name>David Miller</name>
<email>davem@davemloft.net</email>
</author>
<published>2006-06-20T07:06:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ac3e4adefd766840f20e7cad6aa430f3fb491c4d'/>
<id>urn:sha1:ac3e4adefd766840f20e7cad6aa430f3fb491c4d</id>
<content type='text'>
Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] SCTP: Reject sctp packets with broadcast addresses.</title>
<updated>2006-06-30T00:17:15Z</updated>
<author>
<name>Vlad Yasevich</name>
<email>vladislav.yasevich@hp.com</email>
</author>
<published>2006-06-20T07:04:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8cd8533a381af92ff3febeb0ab82b4d145be1257'/>
<id>urn:sha1:8cd8533a381af92ff3febeb0ab82b4d145be1257</id>
<content type='text'>
Make SCTP handle broadcast properly

Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] SCTP: Limit association max_retrans setting in setsockopt.</title>
<updated>2006-06-30T00:17:15Z</updated>
<author>
<name>Vlad Yasevich</name>
<email>vladislav.yasevich@hp.com</email>
</author>
<published>2006-06-20T07:04:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=617495463a301a956990b87913849dd740e58bcf'/>
<id>urn:sha1:617495463a301a956990b87913849dd740e58bcf</id>
<content type='text'>
When using ASSOCINFO socket option, we need to limit the number of
maximum association retransmissions to be no greater than the sum
of all the path retransmissions. This is specified in Section 7.1.2
of the SCTP socket API draft.
However, we only do this if the association has multiple paths. If
there is only one path, the protocol stack will use the
assoc_max_retrans setting when trying to retransmit packets.

Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] IPV6: Sum real space for RTAs.</title>
<updated>2006-06-30T00:17:14Z</updated>
<author>
<name>YOSHIFUJI Hideaki</name>
<email>yoshfuji@linux-ipv6.org</email>
</author>
<published>2006-06-20T07:02:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8fbc89242905b7645064d6946ac86d4bd77c55c5'/>
<id>urn:sha1:8fbc89242905b7645064d6946ac86d4bd77c55c5</id>
<content type='text'>
This patch fixes RTNLGRP_IPV6_IFINFO netlink notifications.  Issue
pointed out by Patrick McHardy &lt;kaber@trash.net&gt;.

Signed-off-by: YOSHIFUJI Hideaki &lt;yoshfuji@linux-ipv6.org&gt;
Acked-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] xt_sctp: fix endless loop caused by 0 chunk length (CVE-2006-3085)</title>
<updated>2006-06-20T09:31:42Z</updated>
<author>
<name>Patrick McHardy</name>
<email>kaber@trash.net</email>
</author>
<published>2006-06-19T17:14:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b9d3e52e0e0f95ab5198ac20fbc47b3cb1a63407'/>
<id>urn:sha1:b9d3e52e0e0f95ab5198ac20fbc47b3cb1a63407</id>
<content type='text'>
Fix endless loop in the SCTP match similar to those already fixed in the
SCTP conntrack helper (was CVE-2006-1527).

Signed-off-by: Patrick McHardy &lt;kaber@trash.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
</feed>
