From: Matthieu Baerts <matttbe@kernel.org>
To: Kalpan Jani <kalpan.jani@mpiricsoftware.com>
Cc: mptcp <mptcp@lists.linux.dev>,
"shardul.b" <shardul.b@mpiricsoftware.com>,
janak <janak@mpiric.us>, kalpanjani009 <kalpanjani009@gmail.com>
Subject: Re: [PATCH net-next v2] mptcp: normalize seq numbers reported in mptcp_info
Date: Wed, 2 Sep 2026 09:46:39 +0200 [thread overview]
Message-ID: <c17bc657-e079-482c-9aa1-78327bb651d0@kernel.org> (raw)
In-Reply-To: <1a060e0334d.16e6f547114597.2162647064543858742@mpiricsoftware.com>
Hi Kalpan,
On 02/09/2026 08:48, Kalpan Jani wrote:
> Hi Matt,
>
> You were right, thanks for pushing back on that. I added msk_state to the same debug print and reran mptcp_join.sh - every single instance of msk->first going NULL shows msk_state=7 (TCP_CLOSE), no exceptions across several hundred hits. So it really is only happening as part of the whole msk already being torn down, like you said, not during a live connection.
>
> I'll rework v3 to read idsn/iasn straight off msk->first instead of adding the two new fields, per your suggestion.
Great, thank you for having checked and working on a v3.
BTW, a "detail", but top-posting is not recommended on (kernel) mailing
lists:
https://subspace.kernel.org/etiquette.html#do-not-top-post-when-replying
Also, here, no need to include MPTCP people in cc (Paolo, Mat, myself),
we get such emails via the mailing list.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-09-02 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 4:10 [PATCH net-next v2] mptcp: normalize seq numbers reported in mptcp_info Kalpan Jani
2026-08-27 5:15 ` MPTCP CI
2026-08-31 10:29 ` Matthieu Baerts
2026-09-01 5:19 ` Kalpan Jani
2026-09-01 5:55 ` Matthieu Baerts
2026-09-02 6:48 ` Kalpan Jani
2026-09-02 7:46 ` Matthieu Baerts [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-25 11:33 [PATCH net-next] " Kalpan Jani
2026-08-26 6:03 ` [PATCH net-next v2] " Kalpan Jani
2026-08-26 7:26 ` MPTCP CI
2026-08-26 9:48 ` Kalpan Jani
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=c17bc657-e079-482c-9aa1-78327bb651d0@kernel.org \
--to=matttbe@kernel.org \
--cc=janak@mpiric.us \
--cc=kalpan.jani@mpiricsoftware.com \
--cc=kalpanjani009@gmail.com \
--cc=mptcp@lists.linux.dev \
--cc=shardul.b@mpiricsoftware.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