[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKgT0UdSRi-iwZpBWrezg=-fFcVTFSd=2FOOye_oZr2oNCNJAw@mail.gmail.com>
Date: Mon, 11 Jan 2016 10:39:40 -0800
From: Alexander Duyck <alexander.duyck@...il.com>
To: Edward Cree <ecree@...arflare.com>
Cc: David Laight <David.Laight@...lab.com>,
David Miller <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-net-drivers@...arflare.com" <linux-net-drivers@...arflare.com>,
"tom@...bertland.com" <tom@...bertland.com>
Subject: Re: [PATCH net-next 6/8] net: gre: Implement LCO for GRE over IPv4
On Mon, Jan 11, 2016 at 5:21 AM, Edward Cree <ecree@...arflare.com> wrote:
> On 11/01/16 10:09, David Laight wrote:
>> From: Edward Cree
>>> Sent: 08 January 2016 19:47
>> ...
>>> + if (skb->ip_summed == CHECKSUM_PARTIAL) {
>>> + csum = csum_fold(lco_csum(skb));
>>> + if (csum == 0)
>>> + csum = CSUM_MANGLED_0;
>>> + return csum;
>>> + } else {
>>> + return csum_fold(skb_checksum(skb, 0, skb->len, 0));
>>> + }
>> You see to be worried about csum_fold() returning 0 in one
>> path, but not in the other.
>> I'm guessing that 0 can only happen if all the bytes that have
>> been checksummed are zero.
> csum_fold complements, so if the sum comes to (say) 0x1fffe, it will return ~0xffff which is 0.
>
> Next version of patch will mangle 0 for both branches.
Actually you may want to go the other way on that. If they weren't
flipping the checksum value for GRE before why should we start doing
that now? I'm pretty sure the checksum mangling is a very UDP centric
thing. There is no need to introduce it to other protocols.
- Alex
Powered by blists - more mailing lists