From: Matthieu Baerts <matttbe@kernel.org>
To: Tao Cui <cui.tao@linux.dev>, gang.yan@linux.dev, mptcp@lists.linux.dev
Cc: martineau@kernel.org, geliang@kernel.org, Tao Cui <cuitao@kylinos.cn>
Subject: Re: [RFC PATCH mptcp-next] mptcp: annotate data-races around sysctl reads
Date: Sat, 15 Aug 2026 00:36:50 +0200 [thread overview]
Message-ID: <899ba654-b0cb-49a1-a481-884734985b77@kernel.org> (raw)
In-Reply-To: <d446f4a1-f100-453e-a952-5353505a465a@linux.dev>
Hi Tao, Gang,
Thank you for looking at this!
On 14/08/2026 07:26, Tao Cui wrote:
> Hi Gang,
>
> 在 2026/8/14 11:51, gang.yan@linux.dev 写道:
>> August 14, 2026 at 11:27 AM, "Tao Cui" <cui.tao@linux.dev mailto:cui.tao@linux.dev?to=%22Tao%20Cui%22%20%3Ccui.tao%40linux.dev%3E > wrote:
>>
>> Hi, Tao
>>
>> Thanks for your patch, but it has been submitted by Matt before in [1].
Thank you for the review!
>> I think Matt wanted change the PM and sched sysctl from string to atomically,
>> that may need another patches (READ_ONCE is not enough), right? If no, you can
>> wait for the other maintainers' reply.
Correct.
>> If yes, I still think this patch should keep author as matt, the rest of
>> others can be yours.
>>
>> Note: Some patches about sched is only in our export branch, not mainlined,
>> so it's better to do your work based on it.
>>
>
> Thanks for the review. I did see #626 before sending and referenced
> it, I just read its scope wrong: I assumed the patch it links was only
> about the string sysctls and missed that the numeric readers were
> already covered there.
Do you plan to work on that? If yes, that's great, thank you. Just one
thing: if you are working on addressing an issue that is on GitHub, do
you mind adding a comment there to say that you are working on it,
please? Just to avoid having multiple people doing the same thing. (Just
to be clear: I'm not working on it.)
> And thanks for the export branch tip, I'd only been looking at
> mainline and didn't know some of the sched patches are only in export.
>
> The only bit mine adds is the WRITE_ONCE() on the pm_type store in
> proc_path_manager(), to pair with the mptcp_get_pm_type() read. Matt,
> if you want that too just grab it, otherwise I can send it as a small
> follow-up.
Good catch! If you are planning to work on the other remaining sysctl,
do you mind taking my patch, add the missing WRITE_ONCE() to it + add
your co-developed-by + signoff to it, then add your new patch(es) on top
of it and send everything (including the first patch), please?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-08-14 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 3:27 [RFC PATCH mptcp-next] mptcp: annotate data-races around sysctl reads Tao Cui
2026-08-14 3:51 ` gang.yan
2026-08-14 5:26 ` Tao Cui
2026-08-14 22:36 ` Matthieu Baerts [this message]
2026-08-14 4:31 ` MPTCP CI
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=899ba654-b0cb-49a1-a481-884734985b77@kernel.org \
--to=matttbe@kernel.org \
--cc=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=gang.yan@linux.dev \
--cc=geliang@kernel.org \
--cc=martineau@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.