<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/net, branch v2.6.35.9</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/net?h=v2.6.35.9</id>
<link rel='self' href='https://git.amat.us/linux/atom/net?h=v2.6.35.9'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2010-11-22T19:00:17Z</updated>
<entry>
<title>secmark: do not return early if there was no error</title>
<updated>2010-11-22T19:00:17Z</updated>
<author>
<name>Eric Paris</name>
<email>eparis@redhat.com</email>
</author>
<published>2010-10-12T15:40:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e0b20e1140f0a2b691cffd28c7ac2a29d59b96ee'/>
<id>urn:sha1:e0b20e1140f0a2b691cffd28c7ac2a29d59b96ee</id>
<content type='text'>
commit 15714f7b58011cf3948cab2988abea560240c74f upstream.

Commit 4a5a5c73 attempted to pass decent error messages back to userspace for
netfilter errors.  In xt_SECMARK.c however the patch screwed up and returned
on 0 (aka no error) early and didn't finish setting up secmark.  This results
in a kernel BUG if you use SECMARK.

Signed-off-by: Eric Paris &lt;eparis@redhat.com&gt;
Acked-by: Paul Moore &lt;paul.moore@hp.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>xfrm4: strip ECN bits from tos field</title>
<updated>2010-11-22T19:00:15Z</updated>
<author>
<name>Ulrich Weber</name>
<email>uweber@astaro.com</email>
</author>
<published>2010-09-22T06:45:11Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=badaad1d7392eebf646b2e2d4dfe2586e40a8f18'/>
<id>urn:sha1:badaad1d7392eebf646b2e2d4dfe2586e40a8f18</id>
<content type='text'>
[ Upstream commit 94e2238969e89f5112297ad2a00103089dde7e8f ]

otherwise ECT(1) bit will get interpreted as RTO_ONLINK
and routing will fail with XfrmOutBundleGenError.

Signed-off-by: Ulrich Weber &lt;uweber@astaro.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>net/core: Allow tagged VLAN packets to flow through VETH devices.</title>
<updated>2010-11-22T19:00:15Z</updated>
<author>
<name>Ben Greear</name>
<email>greearb@candelatech.com</email>
</author>
<published>2010-10-21T11:06:29Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e26158f99c3c79181eb3e314e898079565cc75fd'/>
<id>urn:sha1:e26158f99c3c79181eb3e314e898079565cc75fd</id>
<content type='text'>
[ Upstream commit d2ed817766987fd05e69b7da65d4861b38f1aa2a ]

When there are VLANs on a VETH device, the packets being transmitted
through the VETH device may be 4 bytes bigger than MTU.  A check
in dev_forward_skb did not take this into account and so dropped
these packets.

This patch is needed at least as far back as 2.6.34.7 and should
be considered for -stable.

Signed-off-by: Ben Greear &lt;greearb@candelatech.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>net: add a recursion limit in xmit path</title>
<updated>2010-11-22T19:00:15Z</updated>
<author>
<name>Eric Dumazet</name>
<email>eric.dumazet@gmail.com</email>
</author>
<published>2010-09-29T20:23:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3f266b04185de51d8e6446eb1fccec3b5e7ce575'/>
<id>urn:sha1:3f266b04185de51d8e6446eb1fccec3b5e7ce575</id>
<content type='text'>
[ Upstream commits 745e20f1b626b1be4b100af5d4bf7b3439392f8f and
  11a766ce915fc9f8663714eac6d59239388534ea ]

As tunnel devices are going to be lockless, we need to make sure a
misconfigured machine wont enter an infinite loop.

Add a percpu variable, and limit to three the number of stacked xmits.

Reported-by: Jesse Gross &lt;jesse@nicira.com&gt;
Signed-off-by: Eric Dumazet &lt;eric.dumazet@gmail.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>Revert d88dca79d3852a3623f606f781e013d61486828a</title>
<updated>2010-11-22T19:00:14Z</updated>
<author>
<name>Neil Horman</name>
<email>nhorman@tuxdriver.com</email>
</author>
<published>2010-10-21T01:06:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a3c1c5704f66741f3249926b31cc4a201b1faeda'/>
<id>urn:sha1:a3c1c5704f66741f3249926b31cc4a201b1faeda</id>
<content type='text'>
[ Upstream commit db5a753bf198ef7a50e17d2ff358adf37efe8648 ]

TIPC needs to have its endianess issues fixed.  Unfortunately, the format of a
subscriber message is passed in directly from user space, so requiring this
message to be in network byte order breaks user space ABI.  Revert this change
until such time as we can determine how to do this in a backwards compatible
manner.

Signed-off-by: Neil Horman &lt;nhorman@tuxdriver.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>Revert c6537d6742985da1fbf12ae26cde6a096fd35b5c</title>
<updated>2010-11-22T19:00:13Z</updated>
<author>
<name>Neil Horman</name>
<email>nhorman@tuxdriver.com</email>
</author>
<published>2010-10-21T01:06:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4ac86dc5d9f1407e94253e29b7b6c57517f9abae'/>
<id>urn:sha1:4ac86dc5d9f1407e94253e29b7b6c57517f9abae</id>
<content type='text'>
[ Upstream commit 8c974438085d2c81b006daeaab8801eedbd19758 ]

Backout the tipc changes to the flags int he subscription message.  These
changees, while reasonable on the surface, interefere with user space ABI
compatibility which is a no-no.  This was part of the changes to fix the
endianess issues in the TIPC protocol, which would be really nice to do but we
need to do so in a way that is backwards compatible with user space.

Signed-off-by: Neil Horman &lt;nhorman@tuxdriver.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>net-2.6: SYN retransmits: Add new parameter to retransmits_timed_out()</title>
<updated>2010-11-22T19:00:12Z</updated>
<author>
<name>Damian Lukowski</name>
<email>damian@tvk.rwth-aachen.de</email>
</author>
<published>2010-09-28T20:08:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ea912fae3bb8e465497f0f4c8f3dcb3e9057cf06'/>
<id>urn:sha1:ea912fae3bb8e465497f0f4c8f3dcb3e9057cf06</id>
<content type='text'>
[ Upstream commit 4d22f7d372f5769c6c0149e427ed6353e2dcfe61 ]

Fixes kernel Bugzilla Bug 18952

This patch adds a syn_set parameter to the retransmits_timed_out()
routine and updates its callers. If not set, TCP_RTO_MIN is taken
as the calculation basis as before. If set, TCP_TIMEOUT_INIT is
used instead, so that sysctl_syn_retries represents the actual
amount of SYN retransmissions in case no SYNACKs are received when
establishing a new connection.

Signed-off-by: Damian Lukowski &lt;damian@tvk.rwth-aachen.de&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>tcp: Fix race in tcp_poll</title>
<updated>2010-11-22T19:00:12Z</updated>
<author>
<name>Tom Marshall</name>
<email>tdm.code@gmail.com</email>
</author>
<published>2010-09-20T22:42:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4ba3d9baf1ebfb97ea04384e8b2775744b341268'/>
<id>urn:sha1:4ba3d9baf1ebfb97ea04384e8b2775744b341268</id>
<content type='text'>
[ Upstream commit a4d258036ed9b2a1811c3670c6099203a0f284a0 ]

If a RST comes in immediately after checking sk-&gt;sk_err, tcp_poll will
return POLLIN but not POLLOUT.  Fix this by checking sk-&gt;sk_err at the end
of tcp_poll.  Additionally, ensure the correct order of operations on SMP
machines with memory barriers.

Signed-off-by: Tom Marshall &lt;tdm.code@gmail.com&gt;
Signed-off-by: Eric Dumazet &lt;eric.dumazet@gmail.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>Limit sysctl_tcp_mem and sysctl_udp_mem initializers to prevent integer overflows.</title>
<updated>2010-11-22T19:00:11Z</updated>
<author>
<name>holt@sgi.com</name>
<email>holt@sgi.com</email>
</author>
<published>2010-10-20T02:03:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=56b8700a1069f66ace7575b9cd104f626379f8cd'/>
<id>urn:sha1:56b8700a1069f66ace7575b9cd104f626379f8cd</id>
<content type='text'>
On a 16TB x86_64 machine, sysctl_tcp_mem[2], sysctl_udp_mem[2], and
sysctl_sctp_mem[2] can integer overflow.  Set limit such that they are
maximized without overflowing.

Signed-off-by: Robin Holt &lt;holt@sgi.com&gt;
To: "David S. Miller" &lt;davem@davemloft.net&gt;
Cc: Willy Tarreau &lt;w@1wt.eu&gt;
Cc: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Cc: linux-sctp@vger.kernel.org
Cc: Alexey Kuznetsov &lt;kuznet@ms2.inr.ac.ru&gt;
Cc: "Pekka Savola (ipv6)" &lt;pekkas@netcore.fi&gt;
Cc: James Morris &lt;jmorris@namei.org&gt;
Cc: Hideaki YOSHIFUJI &lt;yoshfuji@linux-ipv6.org&gt;
Cc: Patrick McHardy &lt;kaber@trash.net&gt;
Cc: Vlad Yasevich &lt;vladislav.yasevich@hp.com&gt;
Cc: Sridhar Samudrala &lt;sri@us.ibm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>net: Fix the condition passed to sk_wait_event()</title>
<updated>2010-11-22T19:00:11Z</updated>
<author>
<name>Nagendra Tomar</name>
<email>tomer_iisc@yahoo.com</email>
</author>
<published>2010-10-02T23:45:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=44f89254e4ce18795b2b7b9d1f722e0f6ac4711c'/>
<id>urn:sha1:44f89254e4ce18795b2b7b9d1f722e0f6ac4711c</id>
<content type='text'>
[ Upstream commit 482964e56e1320cb7952faa1932d8ecf59c4bf75 ]

This patch fixes the condition (3rd arg) passed to sk_wait_event() in
sk_stream_wait_memory(). The incorrect check in sk_stream_wait_memory()
causes the following soft lockup in tcp_sendmsg() when the global tcp
memory pool has exhausted.

&gt;&gt;&gt; snip &lt;&lt;&lt;

localhost kernel: BUG: soft lockup - CPU#3 stuck for 11s! [sshd:6429]
localhost kernel: CPU 3:
localhost kernel: RIP: 0010:[sk_stream_wait_memory+0xcd/0x200]  [sk_stream_wait_memory+0xcd/0x200] sk_stream_wait_memory+0xcd/0x200
localhost kernel:
localhost kernel: Call Trace:
localhost kernel:  [sk_stream_wait_memory+0x1b1/0x200] sk_stream_wait_memory+0x1b1/0x200
localhost kernel:  [&lt;ffffffff802557c0&gt;] autoremove_wake_function+0x0/0x40
localhost kernel:  [ipv6:tcp_sendmsg+0x6e6/0xe90] tcp_sendmsg+0x6e6/0xce0
localhost kernel:  [sock_aio_write+0x126/0x140] sock_aio_write+0x126/0x140
localhost kernel:  [xfs:do_sync_write+0xf1/0x130] do_sync_write+0xf1/0x130
localhost kernel:  [&lt;ffffffff802557c0&gt;] autoremove_wake_function+0x0/0x40
localhost kernel:  [hrtimer_start+0xe3/0x170] hrtimer_start+0xe3/0x170
localhost kernel:  [vfs_write+0x185/0x190] vfs_write+0x185/0x190
localhost kernel:  [sys_write+0x50/0x90] sys_write+0x50/0x90
localhost kernel:  [system_call+0x7e/0x83] system_call+0x7e/0x83

&gt;&gt;&gt; snip &lt;&lt;&lt;

What is happening is, that the sk_wait_event() condition passed from
sk_stream_wait_memory() evaluates to true for the case of tcp global memory
exhaustion. This is because both sk_stream_memory_free() and vm_wait are true
which causes sk_wait_event() to *not* call schedule_timeout().
Hence sk_stream_wait_memory() returns immediately to the caller w/o sleeping.
This causes the caller to again try allocation, which again fails and again
calls sk_stream_wait_memory(), and so on.

[ Bug introduced by commit c1cbe4b7ad0bc4b1d98ea708a3fecb7362aa4088
  ("[NET]: Avoid atomic xchg() for non-error case") -DaveM ]

Signed-off-by: Nagendra Singh Tomar &lt;tomer_iisc@yahoo.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>
</feed>
