<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/sctp/outqueue.c, branch linux-2.6.27.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.27.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.27.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-02-17T17:46:19Z</updated>
<entry>
<title>sctp: Correctly start rtx timer on new packet transmissions.</title>
<updated>2009-02-17T17:46:19Z</updated>
<author>
<name>Vlad Yasevich</name>
</author>
<published>2009-01-22T22:52:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0eb599ae814fe658d2b6d1e81795c411812bb71f'/>
<id>urn:sha1:0eb599ae814fe658d2b6d1e81795c411812bb71f</id>
<content type='text'>
[ Upstream commit 6574df9a89f9f7da3a4e5cee7633d430319d3350 ]

Commit 62aeaff5ccd96462b7077046357a6d7886175a57
(sctp: Start T3-RTX timer when fast retransmitting lowest TSN)
introduced a regression where it was possible to forcibly
restart the sctp retransmit timer at the transmission of any
new chunk.  This resulted in much longer timeout times and
sometimes hung sctp connections.

Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>sctp: make sctp_outq_flush() static</title>
<updated>2008-07-22T21:20:45Z</updated>
<author>
<name>Adrian Bunk</name>
</author>
<published>2008-07-22T21:20:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=abd0b198ea699578c3c3476d646c91842e19dbd2'/>
<id>urn:sha1:abd0b198ea699578c3c3476d646c91842e19dbd2</id>
<content type='text'>
sctp_outq_flush() can now become static.

Signed-off-by: Adrian Bunk &lt;bunk@kernel.org&gt;
Acked-by: Neil Horman &lt;nhorman@tuxdriver.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sctp: Follow security requirement of responding with 1 packet</title>
<updated>2008-06-19T23:08:18Z</updated>
<author>
<name>Vlad Yasevich</name>
</author>
<published>2008-06-19T23:08:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2e3216cd54b142ba605e87522e15f42e0c4e3996'/>
<id>urn:sha1:2e3216cd54b142ba605e87522e15f42e0c4e3996</id>
<content type='text'>
RFC 4960, Section 11.4. Protection of Non-SCTP-Capable Hosts

When an SCTP stack receives a packet containing multiple control or
DATA chunks and the processing of the packet requires the sending of
multiple chunks in response, the sender of the response chunk(s) MUST
NOT send more than one packet.  If bundling is supported, multiple
response chunks that fit into a single packet MAY be bundled together
into one single response packet.  If bundling is not supported, then
the sender MUST NOT send more than one response chunk and MUST
discard all other responses.  Note that this rule does NOT apply to a
SACK chunk, since a SACK chunk is, in itself, a response to DATA and
a SACK does not require a response of more DATA.

We implement this by not servicing our outqueue until we reach the end
of the packet.  This enables maximum bundling.  We also identify
'response' chunks and make sure that we only send 1 packet when sending
such chunks.

Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sctp: Flush the queue only once during fast retransmit.</title>
<updated>2008-06-04T19:39:36Z</updated>
<author>
<name>Vlad Yasevich</name>
</author>
<published>2008-06-04T19:39:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8b750ce54bd8ab5f75d519ee450e1b0c5226ebe9'/>
<id>urn:sha1:8b750ce54bd8ab5f75d519ee450e1b0c5226ebe9</id>
<content type='text'>
When fast retransmit is triggered by a sack, we should flush the queue
only once so that only 1 retransmit happens.  Also, since we could
potentially have non-fast-rtx chunks on the retransmit queue, we need
make sure any chunks eligable for fast retransmit are sent first
during fast retransmission.

Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Tested-by: Wei Yongjun &lt;yjwei@cn.fujitsu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>sctp: Start T3-RTX timer when fast retransmitting lowest TSN</title>
<updated>2008-06-04T19:39:11Z</updated>
<author>
<name>Vlad Yasevich</name>
</author>
<published>2008-06-04T19:39:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=62aeaff5ccd96462b7077046357a6d7886175a57'/>
<id>urn:sha1:62aeaff5ccd96462b7077046357a6d7886175a57</id>
<content type='text'>
When we are trying to fast retransmit the lowest outstanding TSN, we
need to restart the T3-RTX timer, so that subsequent timeouts will
correctly tag all the packets necessary for retransmissions.

Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Tested-by: Wei Yongjun &lt;yjwei@cn.fujitsu.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>SCTP: Initialize partial_bytes_acked to 0, when all of the data is acked.</title>
<updated>2008-04-17T21:22:18Z</updated>
<author>
<name>Gui Jianfeng</name>
</author>
<published>2008-04-17T21:22:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8b73a07c8ffaa70683022566080f4df3328ea18d'/>
<id>urn:sha1:8b73a07c8ffaa70683022566080f4df3328ea18d</id>
<content type='text'>
According to RFC4960 7.2.2, 
When all of the data transmitted by the sender has
been acknowledged by the recerver, partial_bytes_acked is initialized to 0.

This patch conforms to rfc requirement. 
Without this fix, cwnd might be error incremented.

Signed-off-by: Gui Jianfeng &lt;guijianfeng@cn.fujitsu.com&gt;
Acked-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6</title>
<updated>2008-04-14T09:30:23Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2008-04-14T09:30:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=df39e8ba56a788733d369068c7319e04b1da3cd5'/>
<id>urn:sha1:df39e8ba56a788733d369068c7319e04b1da3cd5</id>
<content type='text'>
Conflicts:

	drivers/net/ehea/ehea_main.c
	drivers/net/wireless/iwlwifi/Kconfig
	drivers/net/wireless/rt2x00/rt61pci.c
	net/ipv4/inet_timewait_sock.c
	net/ipv6/raw.c
	net/mac80211/ieee80211_sta.c
</content>
</entry>
<entry>
<title>[SCTP]: "list_for_each()" -&gt; "list_for_each_entry()" where appropriate.</title>
<updated>2008-04-13T01:54:24Z</updated>
<author>
<name>Robert P. J. Day</name>
</author>
<published>2008-04-13T01:54:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9dbc15f055f05393ace4f1733f160ec3d188cf9b'/>
<id>urn:sha1:9dbc15f055f05393ace4f1733f160ec3d188cf9b</id>
<content type='text'>
Replacing (almost) all invocations of list_for_each() with
list_for_each_entry() tightens up the code and allows for the deletion
of numerous list iterator variables that are no longer necessary.

Signed-off-by: Robert P. J. Day &lt;rpjday@crashcourse.ca&gt;
Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>[SCTP]: Fix protocol violation when receiving an error lenght INIT-ACK</title>
<updated>2008-04-13T01:39:34Z</updated>
<author>
<name>Gui Jianfeng</name>
</author>
<published>2008-04-13T01:39:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f4ad85ca3ef8a1ede76c5020a28a8f4057b4d24f'/>
<id>urn:sha1:f4ad85ca3ef8a1ede76c5020a28a8f4057b4d24f</id>
<content type='text'>
When receiving an error length INIT-ACK during COOKIE-WAIT,
a 0-vtag ABORT will be responsed. This action violates the
protocol apparently. This patch achieves the following things.
1 If the INIT-ACK contains all the fixed parameters, use init-tag
  recorded from INIT-ACK as vtag.
2 If the INIT-ACK doesn't contain all the fixed parameters,
  just reflect its vtag.

Signed-off-by: Gui Jianfeng &lt;guijianfeng@cn.fujitsu.com&gt;
Signed-off-by: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: replace remaining __FUNCTION__ occurrences</title>
<updated>2008-03-06T04:47:47Z</updated>
<author>
<name>Harvey Harrison</name>
</author>
<published>2008-03-06T04:47:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0dc47877a3de00ceadea0005189656ae8dc52669'/>
<id>urn:sha1:0dc47877a3de00ceadea0005189656ae8dc52669</id>
<content type='text'>
__FUNCTION__ is gcc-specific, use __func__

Signed-off-by: Harvey Harrison &lt;harvey.harrison@gmail.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
