From: gang.yan@linux.dev
To: "Matthieu Baerts" <matttbe@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net] mptcp: sockopt: set timestamp flags on subflow socket, not msk
Date: Wed, 22 Apr 2026 05:52:21 +0000 [thread overview]
Message-ID: <091162cb30a989b1a46612cc3f1a2879935edfec@linux.dev> (raw)
In-Reply-To: <0709c747-463f-4f5f-995b-156764f35da3@kernel.org>
April 20, 2026 at 5:46 PM, "Matthieu Baerts" <matttbe@kernel.org mailto:matttbe@kernel.org?to=%22Matthieu%20Baerts%22%20%3Cmatttbe%40kernel.org%3E > wrote:
>
> Hi Gang,
>
> On 20/04/2026 11:33, Gang Yan wrote:
>
> >
> > From: Gang Yan <yangang@kylinos.cn>
> >
> > Both mptcp_setsockopt_sol_socket_tstamp() and
> > mptcp_setsockopt_sol_socket_timestamping() iterate over subflows,
> > acquire the subflow socket lock, but then erroneously pass the MPTCP
> > msk socket to sock_set_timestamp() / sock_set_timestamping() instead
> > of the subflow ssk. As a result, the timestamp flags are set on the
> > wrong socket and have no effect on the actual subflows.
> >
> > Pass ssk instead of sk to both helpers.
> >
> Good catch! How did you find the issue? It would be good to add a test
> for that, but not sure how.
>
Hi Matt,
Sorry for the late feedback.
Thanks! I’ve been using AI assistance to study and understand this part of
the code recently, and that’s how I found the issue.
And I noticed the issue of sashiko mentioned. I’ll take time to look into it
recently, and I will post updates on this issue to the mailing list.
Thanks
Gang
> >
> > Fixes: 3f4f958c3a3c ("mptcp: sockopt: propagate timestamp request to subflows")
> >
> It looks like this commit doesn't exist in the 'export' or 'export-net'
> branches. I guess you meant to use 9061f24bf82e instead?
>
> When you do a git blame, do not use branches from the TopGit tree. Use
> 'net', 'net-next', or the 'export' ones.
>
> >
> > Fixes: 6c9a0a0f2333 ("mptcp: setsockopt: convert to mptcp_setsockopt_sol_socket_timestamping()")
> > Assisted-by: GLM-5.1
> >
> Thank you for using this tag!
>
> Apart from the above, it looks good to me:
>
> Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
> I will wait for the CI, but I can also fix the SHA (if correct) when
> applying the patch.
>
> Cheers,
> Matt
> --
> Sponsored by the NGI0 Core fund.
>
next prev parent reply other threads:[~2026-04-22 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 9:33 [PATCH mptcp-net] mptcp: sockopt: set timestamp flags on subflow socket, not msk Gang Yan
2026-04-20 9:46 ` Matthieu Baerts
2026-04-20 10:07 ` Matthieu Baerts
2026-04-21 16:12 ` Matthieu Baerts
2026-04-22 5:52 ` gang.yan [this message]
2026-04-20 11:05 ` MPTCP CI
2026-04-21 16:18 ` 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=091162cb30a989b1a46612cc3f1a2879935edfec@linux.dev \
--to=gang.yan@linux.dev \
--cc=matttbe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox