From: Gang Yan <gang.yan@linux.dev>
To: mptcp@lists.linux.dev
Subject: [PATCH mptcp-next v3 0/5] mptcp: avoid data-races around the sysctls
Date: Wed, 19 Aug 2026 20:56:24 +0800 [thread overview]
Message-ID: <20260819125629.49823-1-gang.yan@linux.dev> (raw)
From: Gang Yan <yangang@kylinos.cn>
Changelog:
v3:
Patch 1:
- Carries the full module refcount handling that was previously
deferred to a squash-to patch.
- mptcp_get_scheduler now returns the ops pointer directly instead
of copying the name, so mptcp_init_sock() no longer goes through a
redundant mptcp_sched_find() list walk.
- A new pernet-level helper 'mptcp_pernet_sched' is shared with
proc_scheduler().
- mptcp_net_init releases the default reference on the
mptcp_pernet_new_table error path.
- Simplify the commit message.
Patch 2:
- Introduce the pernet-level helper mptcp_pernet_pm, like sched
does.
- Commit message shows why no moudule reference is taken here for
addressing sashiko's comments.
Patch 3:
- Remove the WRITE_ONCE() part and the tag of Tao Cui.
Patch 4:
- It is new in this seires. Followed by Matt's suggestions, add
comments before pm_type was changes.
Patch 5:
- Release the PM reference on the mptcp_net_init errpr path as sched
does.
- mptcp_pm_ops_init() now takes the ops pointer directly instead of
the name, and mptcp_get_path_manager() returns the ops pointer:
the redundant mptcp_pm_find() list walk from the name is avoided,
mirroring the scheduler side earlier in this series.
v2:
- Split the code around bpf to patch 4 and patch 5.
- Put WRITE_ONCE(pernet->pm_type, pm_type) into patch 3 and add
tag of Tao Cui.
Link: https://patchwork.kernel.org/project/mptcp/cover/20260818094825.48446-1-gang.yan@linux.dev/
v1:
Link: https://patchwork.kernel.org/project/mptcp/cover/20260817012452.7519-1-gang.yan@linux.dev/
Gang Yan (4):
mptcp: sched: change scheduler sysctl atomically
mptcp: pm: change path_manager sysctl atomically
mptcp: pm: use WRITE_ONCE() for the pm_type sysctl
Squash to "mptcp: pm: init and release mptcp_pm_ops"
Matthieu Baerts (NGI0) (1):
mptcp: use READ_ONCE() over sysctls
net/mptcp/ctrl.c | 141 ++++++++++++++++++++++++++++++++-----------
net/mptcp/pm.c | 11 ++--
net/mptcp/protocol.c | 3 +-
net/mptcp/protocol.h | 6 +-
net/mptcp/sched.c | 2 +-
5 files changed, 115 insertions(+), 48 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-19 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:56 Gang Yan [this message]
2026-08-19 12:56 ` [PATCH mptcp-next v3 1/5] mptcp: sched: change scheduler sysctl atomically Gang Yan
2026-08-19 12:56 ` [PATCH mptcp-next v3 2/5] mptcp: pm: change path_manager " Gang Yan
2026-08-19 12:56 ` [PATCH mptcp-next v3 3/5] mptcp: use READ_ONCE() over sysctls Gang Yan
2026-08-19 12:56 ` [PATCH mptcp-next v3 4/5] mptcp: pm: use WRITE_ONCE() for the pm_type sysctl Gang Yan
2026-08-19 12:56 ` [PATCH mptcp-next v3 5/5] Squash to "mptcp: pm: init and release mptcp_pm_ops" Gang Yan
2026-08-19 13:12 ` sashiko-bot
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=20260819125629.49823-1-gang.yan@linux.dev \
--to=gang.yan@linux.dev \
--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