From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, Mat Martineau <martineau@kernel.org>
Cc: Christoph Paasch <cpaasch@apple.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH net-next] mptcp: deal with large GSO size.
Date: Tue, 7 Nov 2023 22:12:18 +0100 [thread overview]
Message-ID: <0acde784-2d42-42ee-8a43-510f89f7ab39@kernel.org> (raw)
In-Reply-To: <ce93989da39fd2e47baa4506fbbf4c2049c2da13.1698416467.git.pabeni@redhat.com>
Hi Paolo, Mat,
On 27/10/2023 16:21, Paolo Abeni wrote:
> After the blamed commit below, the TCP sockets (and the MPTCP subflows)
> can build egress packets larger then 64K. That exceeds the maximum DSS
> data size, the length being misrepresent on the wire and the stream being
> corrupted, as later observed on the receiver:
Thank you for the patch and the review!
Now in our tree (fix for -net) with Mat's RvB tag:
New patches for t/upstream-net and t/upstream:
- 6ee098165aec: mptcp: deal with large GSO size
- Results: 9fa919e1e582..f1fb06db6c5f (export-net)
- Results: fd17d7e00023..58f8fd527fbf (export)
Tests are now in progress:
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export-net/20231107T210949
https://cirrus-ci.com/github/multipath-tcp/mptcp_net-next/export/20231107T210949
Cheers,
Matt
prev parent reply other threads:[~2023-11-07 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 14:21 [PATCH net-next] mptcp: deal with large GSO size Paolo Abeni
2023-10-27 14:42 ` mptcp: deal with large GSO size.: Build Failure MPTCP CI
2023-10-27 14:59 ` Paolo Abeni
2023-10-31 17:31 ` Matthieu Baerts
2023-10-27 14:46 ` [PATCH net-next] mptcp: deal with large GSO size Paolo Abeni
2023-11-01 23:55 ` Mat Martineau
2023-10-27 16:41 ` mptcp: deal with large GSO size.: Tests Results MPTCP CI
2023-10-31 17:26 ` MPTCP CI
2023-11-07 17:23 ` [PATCH net-next] mptcp: deal with large GSO size Mat Martineau
2023-11-07 18:58 ` mptcp: deal with large GSO size.: Tests Results MPTCP CI
2023-11-07 21:12 ` Matthieu Baerts [this message]
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=0acde784-2d42-42ee-8a43-510f89f7ab39@kernel.org \
--to=matttbe@kernel.org \
--cc=cpaasch@apple.com \
--cc=martineau@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.