summaryrefslogtreecommitdiffstats
path: root/samples
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2017-07-31 16:52:36 +0200
committerDavid S. Miller <davem@davemloft.net>2017-07-31 22:01:21 -0700
commitcb891fa6a1d5f52c5f5c07b6f7f4c6d65ea55fc0 (patch)
treebd5ac01acb50fe8873102d5d3084ee2cc1c73548 /samples
parentddab82821fa633da768879fc515e76dcb1207151 (diff)
downloadlinux-cb891fa6a1d5f52c5f5c07b6f7f4c6d65ea55fc0.tar.gz
linux-cb891fa6a1d5f52c5f5c07b6f7f4c6d65ea55fc0.tar.bz2
linux-cb891fa6a1d5f52c5f5c07b6f7f4c6d65ea55fc0.zip
udp6: fix jumbogram reception
Since commit 67a51780aebb ("ipv6: udp: leverage scratch area helpers") udp6_recvmsg() read the skb len from the scratch area, to avoid a cache miss. But the UDP6 rx path support RFC 2675 UDPv6 jumbograms, and their length exceeds the 16 bits available in the scratch area. As a side effect the length returned by recvmsg() is: <ingress datagram len> % (1<<16) This commit addresses the issue allocating one more bit in the IP6CB flags field and setting it for incoming jumbograms. Such field is still in the first cacheline, so at recvmsg() time we can check it and fallback to access skb->len if required, without a measurable overhead. Fixes: 67a51780aebb ("ipv6: udp: leverage scratch area helpers") Signed-off-by: Paolo Abeni <pabeni@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions