<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/core/skbuff.c, branch linux-3.15.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.15.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.15.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2014-08-14T01:51:49Z</updated>
<entry>
<title>net: Correctly set segment mac_len in skb_segment().</title>
<updated>2014-08-14T01:51:49Z</updated>
<author>
<name>Vlad Yasevich</name>
</author>
<published>2014-07-31T14:33:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=05e5849764bc807b833598d9a5f0fa1d5ae2ff1f'/>
<id>urn:sha1:05e5849764bc807b833598d9a5f0fa1d5ae2ff1f</id>
<content type='text'>
[ Upstream commit fcdfe3a7fa4cb74391d42b6a26dc07c20dab1d82 ]

When performing segmentation, the mac_len value is copied right
out of the original skb.  However, this value is not always set correctly
(like when the packet is VLAN-tagged) and we'll end up copying a bad
value.

One way to demonstrate this is to configure a VM which tags
packets internally and turn off VLAN acceleration on the forwarding
bridge port.  The packets show up corrupt like this:
16:18:24.985548 52:54:00:ab:be:25 &gt; 52:54:00:26:ce:a3, ethertype 802.1Q
(0x8100), length 1518: vlan 100, p 0, ethertype 0x05e0,
        0x0000:  8cdb 1c7c 8cdb 0064 4006 b59d 0a00 6402 ...|...d@.....d.
        0x0010:  0a00 6401 9e0d b441 0a5e 64ec 0330 14fa ..d....A.^d..0..
        0x0020:  29e3 01c9 f871 0000 0101 080a 000a e833)....q.........3
        0x0030:  000f 8c75 6e65 7470 6572 6600 6e65 7470 ...unetperf.netp
        0x0040:  6572 6600 6e65 7470 6572 6600 6e65 7470 erf.netperf.netp
        0x0050:  6572 6600 6e65 7470 6572 6600 6e65 7470 erf.netperf.netp
        0x0060:  6572 6600 6e65 7470 6572 6600 6e65 7470 erf.netperf.netp
        ...

This also leads to awful throughput as GSO packets are dropped and
cause retransmissions.

The solution is to set the mac_len using the values already available
in then new skb.  We've already adjusted all of the header offset, so we
might as well correctly figure out the mac_len using skb_reset_mac_len().
After this change, packets are segmented correctly and performance
is restored.

CC: Eric Dumazet &lt;edumazet@google.com&gt;
Signed-off-by: Vlad Yasevich &lt;vyasevic@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>net: fix UDP tunnel GSO of frag_list GRO packets</title>
<updated>2014-07-28T15:08:23Z</updated>
<author>
<name>Wei-Chun Chao</name>
</author>
<published>2014-06-09T06:48:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d5edc54bdcd1996389182a3a6654cf87b4ce23cb'/>
<id>urn:sha1:d5edc54bdcd1996389182a3a6654cf87b4ce23cb</id>
<content type='text'>
[ Upstream commit 5882a07c72093dc3a18e2d2b129fb200686bb6ee ]

This patch fixes a kernel BUG_ON in skb_segment. It is hit when
testing two VMs on openvswitch with one VM acting as VXLAN gateway.

During VXLAN packet GSO, skb_segment is called with skb-&gt;data
pointing to inner TCP payload. skb_segment calls skb_network_protocol
to retrieve the inner protocol. skb_network_protocol actually expects
skb-&gt;data to point to MAC and it calls pskb_may_pull with ETH_HLEN.
This ends up pulling in ETH_HLEN data from header tail. As a result,
pskb_trim logic is skipped and BUG_ON is hit later.

Move skb_push in front of skb_network_protocol so that skb-&gt;data
lines up properly.

kernel BUG at net/core/skbuff.c:2999!
Call Trace:
[&lt;ffffffff816ac412&gt;] tcp_gso_segment+0x122/0x410
[&lt;ffffffff816bc74c&gt;] inet_gso_segment+0x13c/0x390
[&lt;ffffffff8164b39b&gt;] skb_mac_gso_segment+0x9b/0x170
[&lt;ffffffff816b3658&gt;] skb_udp_tunnel_segment+0xd8/0x390
[&lt;ffffffff816b3c00&gt;] udp4_ufo_fragment+0x120/0x140
[&lt;ffffffff816bc74c&gt;] inet_gso_segment+0x13c/0x390
[&lt;ffffffff8109d742&gt;] ? default_wake_function+0x12/0x20
[&lt;ffffffff8164b39b&gt;] skb_mac_gso_segment+0x9b/0x170
[&lt;ffffffff8164b4d0&gt;] __skb_gso_segment+0x60/0xc0
[&lt;ffffffff8164b6b3&gt;] dev_hard_start_xmit+0x183/0x550
[&lt;ffffffff8166c91e&gt;] sch_direct_xmit+0xfe/0x1d0
[&lt;ffffffff8164bc94&gt;] __dev_queue_xmit+0x214/0x4f0
[&lt;ffffffff8164bf90&gt;] dev_queue_xmit+0x10/0x20
[&lt;ffffffff81687edb&gt;] ip_finish_output+0x66b/0x890
[&lt;ffffffff81688a58&gt;] ip_output+0x58/0x90
[&lt;ffffffff816c628f&gt;] ? fib_table_lookup+0x29f/0x350
[&lt;ffffffff816881c9&gt;] ip_local_out_sk+0x39/0x50
[&lt;ffffffff816cbfad&gt;] iptunnel_xmit+0x10d/0x130
[&lt;ffffffffa0212200&gt;] vxlan_xmit_skb+0x1d0/0x330 [vxlan]
[&lt;ffffffffa02a3919&gt;] vxlan_tnl_send+0x129/0x1a0 [openvswitch]
[&lt;ffffffffa02a2cd6&gt;] ovs_vport_send+0x26/0xa0 [openvswitch]
[&lt;ffffffffa029931e&gt;] do_output+0x2e/0x50 [openvswitch]

Signed-off-by: Wei-Chun Chao &lt;weichunc@plumgrid.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>net: gro: make sure skb-&gt;cb[] initial content has not to be zero</title>
<updated>2014-05-16T21:24:54Z</updated>
<author>
<name>Eric Dumazet</name>
</author>
<published>2014-05-16T18:34:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=29e98242783ed3ba569797846a606ba66f781625'/>
<id>urn:sha1:29e98242783ed3ba569797846a606ba66f781625</id>
<content type='text'>
Starting from linux-3.13, GRO attempts to build full size skbs.

Problem is the commit assumed one particular field in skb-&gt;cb[]
was clean, but it is not the case on some stacked devices.

Timo reported a crash in case traffic is decrypted before
reaching a GRE device.

Fix this by initializing NAPI_GRO_CB(skb)-&gt;last at the right place,
this also removes one conditional.

Thanks a lot to Timo for providing full reports and bisecting this.

Fixes: 8a29111c7ca6 ("net: gro: allow to build full sized skb")
Bisected-by: Timo Teras &lt;timo.teras@iki.fi&gt;
Signed-off-by: Eric Dumazet &lt;edumazet@google.com&gt;
Tested-by: Timo Teräs &lt;timo.teras@iki.fi&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: Fix use after free by removing length arg from sk_data_ready callbacks.</title>
<updated>2014-04-11T20:15:36Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2014-04-11T20:15:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=676d23690fb62b5d51ba5d659935e9f7d9da9f8e'/>
<id>urn:sha1:676d23690fb62b5d51ba5d659935e9f7d9da9f8e</id>
<content type='text'>
Several spots in the kernel perform a sequence like:

	skb_queue_tail(&amp;sk-&gt;s_receive_queue, skb);
	sk-&gt;sk_data_ready(sk, skb-&gt;len);

But at the moment we place the SKB onto the socket receive queue it
can be consumed and freed up.  So this skb-&gt;len access is potentially
to freed up memory.

Furthermore, the skb-&gt;len can be modified by the consumer so it is
possible that the value isn't accurate.

And finally, no actual implementation of this callback actually uses
the length argument.  And since nobody actually cared about it's
value, lots of call sites pass arbitrary values in such as '0' and
even '1'.

So just remove the length argument from the callback, that way there
is no confusion whatsoever and all of these use-after-free cases get
fixed as a side effect.

Based upon a patch by Eric Dumazet and his suggestion to audit this
issue tree-wide.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: core: don't account for udp header size when computing seglen</title>
<updated>2014-04-11T01:41:25Z</updated>
<author>
<name>Florian Westphal</name>
</author>
<published>2014-04-09T08:28:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6d39d589bb76ee8a1c6cde6822006ae0053decff'/>
<id>urn:sha1:6d39d589bb76ee8a1c6cde6822006ae0053decff</id>
<content type='text'>
In case of tcp, gso_size contains the tcpmss.

For UFO (udp fragmentation offloading) skbs, gso_size is the fragment
payload size, i.e. we must not account for udp header size.

Otherwise, when using virtio drivers, a to-be-forwarded UFO GSO packet
will be needlessly fragmented in the forward path, because we think its
individual segments are too large for the outgoing link.

Fixes: fe6cc55f3a9a053 ("net: ip, ipv6: handle gso skbs in forwarding path")
Cc: Eric Dumazet &lt;eric.dumazet@gmail.com&gt;
Reported-by: Tobias Brunner &lt;tobias@strongswan.org&gt;
Signed-off-by: Florian Westphal &lt;fw@strlen.de&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2014-03-29T22:48:54Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2014-03-29T22:48:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=64c27237a07129758e33f5f824ba5c33b7f57417'/>
<id>urn:sha1:64c27237a07129758e33f5f824ba5c33b7f57417</id>
<content type='text'>
Conflicts:
	drivers/net/ethernet/marvell/mvneta.c

The mvneta.c conflict is a case of overlapping changes,
a conversion to devm_ioremap_resource() vs. a conversion
to netdev_alloc_pcpu_stats.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>net: Account for all vlan headers in skb_mac_gso_segment</title>
<updated>2014-03-28T21:10:36Z</updated>
<author>
<name>Vlad Yasevich</name>
</author>
<published>2014-03-27T21:26:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=53d6471cef17262d3ad1c7ce8982a234244f68ec'/>
<id>urn:sha1:53d6471cef17262d3ad1c7ce8982a234244f68ec</id>
<content type='text'>
skb_network_protocol() already accounts for multiple vlan
headers that may be present in the skb.  However, skb_mac_gso_segment()
doesn't know anything about it and assumes that skb-&gt;mac_len
is set correctly to skip all mac headers.  That may not
always be the case.  If we are simply forwarding the packet (via
bridge or macvtap), all vlan headers may not be accounted for.

A simple solution is to allow skb_network_protocol to return
the vlan depth it has calculated.  This way skb_mac_gso_segment
will correctly skip all mac headers.

Signed-off-by: Vlad Yasevich &lt;vyasevic@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>core, nfqueue, openvswitch: Orphan frags in skb_zerocopy and handle errors</title>
<updated>2014-03-27T19:29:38Z</updated>
<author>
<name>Zoltan Kiss</name>
</author>
<published>2014-03-26T22:37:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=36d5fe6a000790f56039afe26834265db0a3ad4c'/>
<id>urn:sha1:36d5fe6a000790f56039afe26834265db0a3ad4c</id>
<content type='text'>
skb_zerocopy can copy elements of the frags array between skbs, but it doesn't
orphan them. Also, it doesn't handle errors, so this patch takes care of that
as well, and modify the callers accordingly. skb_tx_error() is also added to
the callers so they will signal the failed delivery towards the creator of the
skb.

Signed-off-by: Zoltan Kiss &lt;zoltan.kiss@citrix.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2014-03-15T02:31:55Z</updated>
<author>
<name>David S. Miller</name>
</author>
<published>2014-03-15T02:31:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=85dcce7a73f1cc59f7a96fe52713b1630f4ca272'/>
<id>urn:sha1:85dcce7a73f1cc59f7a96fe52713b1630f4ca272</id>
<content type='text'>
Conflicts:
	drivers/net/usb/r8152.c
	drivers/net/xen-netback/netback.c

Both the r8152 and netback conflicts were simple overlapping
changes.

Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>consolidate duplicate code is skb_checksum_setup() helpers</title>
<updated>2014-03-13T19:16:29Z</updated>
<author>
<name>Jan Beulich</name>
</author>
<published>2014-03-11T13:56:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f9708b4302733ca023722fddcf9f501a3cb8c98b'/>
<id>urn:sha1:f9708b4302733ca023722fddcf9f501a3cb8c98b</id>
<content type='text'>
consolidate duplicate code is skb_checksum_setup() helpers

Realizing that the skb_maybe_pull_tail() calls in the IP-protocol
specific portions of both helpers are terminal ones (i.e. no further
pulls are expected), their maximum size to be pulled can be made match
their minimal size needed, thus making the code identical and hence
possible to be moved into another helper.

Signed-off-by: Jan Beulich &lt;jbeulich@suse.com&gt;
Cc: Paul Durrant &lt;paul.durrant@citrix.com&gt;
Cc: David Miller &lt;davem@davemloft.net&gt;
Cc: Eric Dumazet &lt;edumazet@google.com&gt;
Reviewed-by: Paul Durrant &lt;paul.durrant@citrix.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
