All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] mptcp: validate maxseg sockopt
Date: Thu, 8 May 2025 11:05:45 +0200	[thread overview]
Message-ID: <c2827259-e58b-4d7f-9e38-91cf7f517112@kernel.org> (raw)
In-Reply-To: <dd08686eee5b757ba526e3da3c062894655f56f3.camel@kernel.org>

Hi Geliang,

On 08/05/2025 09:21, Geliang Tang wrote:
> Hi Matt,
> 
> Thanks for the review.
> 
> On Wed, 2025-04-30 at 11:42 +0200, Matthieu Baerts wrote:
>> Hi Geliang,
>>
>> On 30/04/2025 07:49, Geliang Tang wrote:
>>> This patch validates the newly added TCP_MAXSEG sockopt.
>>
>> If you don't mind and have access, do you mind creating a PR on
>> GitHub
>> instead please?
> 
> Here's the PR:
> 
> https://github.com/multipath-tcp/packetdrill/pull/161

Thanks, I just did a review:

  https://github.com/multipath-tcp/packetdrill/pull/161/files

(...)

> In this PR, I almost addressed all your comments above ...
> 
>> Then, if you don't mind, please also create a new subflow by
>> injecting
>> an MP_JOIN with a MSS of 1460, and check that the SYN+ACK+MP_JOIN
>> generated by the kernel has a MSS of 1000 as expected. For an
>> example,
>> check mptcp/mp_join/mp_join_server.pkt.
> 
> But I still have some problems when creating a new subflow, which will
> be added later.

Do not hesitate to share this WIP code and the error you have on the PR.
I also added a few pointers there.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


      reply	other threads:[~2025-05-08  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30  5:49 [PATCH mptcp-next v3 0/2] Add TCP_MAXSEG socket option support Geliang Tang
2025-04-30  5:49 ` [PATCH mptcp-next v3 1/2] tcp: add tcp_sock_set_maxseg Geliang Tang
2025-04-30  5:49 ` [PATCH mptcp-next v3 2/2] mptcp: add TCP_MAXSEG sockopt support Geliang Tang
2025-04-30  8:55   ` Matthieu Baerts
2025-05-06  2:36     ` Geliang Tang
2025-04-30  9:06   ` Matthieu Baerts
2025-04-30  5:49 ` [PATCH mptcp-next] mptcp: validate maxseg sockopt Geliang Tang
2025-04-30  7:15   ` MPTCP CI
2025-04-30  7:31   ` MPTCP CI
2025-04-30  9:42   ` Matthieu Baerts
2025-05-08  7:21     ` Geliang Tang
2025-05-08  9:05       ` 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=c2827259-e58b-4d7f-9e38-91cf7f517112@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    /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.