diff options
| author | David S. Miller <davem@davemloft.net> | 2019-01-26 00:37:11 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2019-01-26 00:37:51 -0500 |
| commit | dda6a7a3685bb1c35d3b500ab83d9780d681d69d (patch) | |
| tree | 299dc0f94d0626e3f75d61450507135f0892389d /net/ipv4/tcp_output.c | |
| parent | ccaceadc4effcb83bb5e84026b6f23c1ae3e0608 (diff) | |
| parent | 4c3510483d26420d2c2c7cc075ad872286cc5932 (diff) | |
Merge branch 'ipv6-defrag-rbtree'
Peter Oskolkov says:
====================
net: IP defrag: use rbtrees in IPv6 defragmentation
Currently, IPv6 defragmentation code drops non-last fragments that
are smaller than 1280 bytes: see
commit 0ed4229b08c1 ("ipv6: defrag: drop non-last frags smaller than min mtu")
This behavior is not specified in IPv6 RFCs and appears to break compatibility
with some IPv6 implementations, as reported here:
https://www.spinics.net/lists/netdev/msg543846.html
This patchset contains four patches:
- patch 1 moves rbtree-related code from IPv4 to files shared b/w
IPv4/IPv6
- patch 2 changes IPv6 defragmenation code to use rbtrees for defrag
queue
- patch 3 changes nf_conntrack IPv6 defragmentation code to use rbtrees
- patch 4 changes ip_defrag selftest to test changes made in the
previous three patches.
Along the way, the 1280-byte restrictions are removed.
I plan to introduce similar changes to 6lowpan defragmentation code
once I figure out how to test it.
====================
Reviewed-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/tcp_output.c')
0 files changed, 0 insertions, 0 deletions