diff options
author | Eric Dumazet <edumazet@google.com> | 2014-05-29 08:45:14 -0700 |
---|---|---|
committer | Ben Hutchings <ben@decadent.org.uk> | 2014-07-11 13:33:57 +0100 |
commit | bd89ed9b75277f5a16f91a2331539dd34a8cf852 (patch) | |
tree | 8a7c303c97dd512489dcad397d0ba84a3d6bcb8a /scripts | |
parent | 30080eb2ea49bff4101b0a3587ae26a590b32c54 (diff) | |
download | kernel_samsung_smdk4412-bd89ed9b75277f5a16f91a2331539dd34a8cf852.zip kernel_samsung_smdk4412-bd89ed9b75277f5a16f91a2331539dd34a8cf852.tar.gz kernel_samsung_smdk4412-bd89ed9b75277f5a16f91a2331539dd34a8cf852.tar.bz2 |
net: fix inet_getid() and ipv6_select_ident() bugs
[ Upstream commit 39c36094d78c39e038c1e499b2364e13bce36f54 ]
I noticed we were sending wrong IPv4 ID in TCP flows when MTU discovery
is disabled.
Note how GSO/TSO packets do not have monotonically incrementing ID.
06:37:41.575531 IP (id 14227, proto: TCP (6), length: 4396)
06:37:41.575534 IP (id 14272, proto: TCP (6), length: 65212)
06:37:41.575544 IP (id 14312, proto: TCP (6), length: 57972)
06:37:41.575678 IP (id 14317, proto: TCP (6), length: 7292)
06:37:41.575683 IP (id 14361, proto: TCP (6), length: 63764)
It appears I introduced this bug in linux-3.1.
inet_getid() must return the old value of peer->ip_id_count,
not the new one.
Lets revert this part, and remove the prevention of
a null identification field in IPv6 Fragment Extension Header,
which is dubious and not even done properly.
Fixes: 87c48fa3b463 ("ipv6: make fragment identifications less predictable")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions