Toke Høiland-Jørgensen 2b714b607f inet_ecn: Fix endianness of checksum update when setting ECT(1)
[ Upstream commit 2867e1eac61016f59b3d730e3f7aa488e186e917 ]

When adding support for propagating ECT(1) marking in IP headers it seems I
suffered from endianness-confusion in the checksum update calculation: In
fact the ECN field is in the *lower* bits of the first 16-bit word of the
IP header when calculating in network byte order. This means that the
addition performed to update the checksum field was wrong; let's fix that.

Fixes: b723748750ec ("tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040")
Reported-by: Jonathan Morton <chromatix99@gmail.com>
Tested-by: Pete Heist <pete@heistp.net>
Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
Link: https://lore.kernel.org/r/20201130183705.17540-1-toke@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2020-12-08 10:40:25 +01:00
..
2019-01-23 11:18:00 -08:00
2019-04-19 14:07:40 -07:00
2019-10-23 20:13:22 -07:00
2020-07-22 09:32:46 +02:00
2019-09-13 21:44:19 +02:00
2018-09-13 09:04:58 -07:00
2019-04-22 21:47:25 -07:00
2019-06-19 11:23:13 -04:00