MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>,
	 Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2] mptcp: fix checksum byte order
Date: Mon, 16 May 2022 16:07:22 -0700 (PDT)	[thread overview]
Message-ID: <314ab5c-3e28-4f49-3afc-82f01c6d2da4@linux.intel.com> (raw)
In-Reply-To: <349fa6a5-6e64-8bce-5592-6164941659b9@tessares.net>


On Sat, 14 May 2022, Matthieu Baerts wrote:

> Hi Paolo, Mat,
>
> On 10/05/2022 18:25, Paolo Abeni wrote:
>> The MPTCP code typecasts the checksum value to u16 and
>> then convert it to big endian while storing the value into
>> the MPTCP option.
>>
>> As a result, the wire encoding for little endian host is
>> wrong, and that causes interoperabilty interoperability
>> issues with other implementation or host with different endianess.
>>
>> Address the issue writing in the packet the unmodified __sum16 value.
>>
>> MPTCP checksum is disabled by default, interoperating with systems
>> with bad mptcp-level csum encodying should cause fallback to TCP.
>
> Thank you for the patch and the review!
>
> Now in our tree (fixes for -net) with Mat's RvB tag:
>
> - 5291df4774c1: mptcp: fix checksum byte order (with conflicts)
> - Results: 128393ceec9b..35e8b300fc90 (export-net)
>

Matthieu, Paolo -

I'm planning to send this patch and "mptcp: Do TCP fallback on early DSS 
checksum failure" to the -net branch on Tuesday - any concerns with that?

Thanks,

--
Mat Martineau
Intel

  reply	other threads:[~2022-05-16 23:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 16:25 [PATCH mptcp-next v2] mptcp: fix checksum byte order Paolo Abeni
2022-05-10 18:36 ` mptcp: fix checksum byte order: Tests Results MPTCP CI
2022-05-10 23:10 ` [PATCH mptcp-next v2] mptcp: fix checksum byte order Mat Martineau
2022-05-11 10:22   ` Paolo Abeni
2022-05-11 15:22     ` Mat Martineau
2022-05-14 17:26 ` Matthieu Baerts
2022-05-16 23:07   ` Mat Martineau [this message]
2022-05-19 14:13     ` Matthieu Baerts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=314ab5c-3e28-4f49-3afc-82f01c6d2da4@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox