MPTCP Linux Development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Gang Yan <gang.yan@linux.dev>, mptcp@lists.linux.dev
Cc: Gang Yan <yangang@kylinos.cn>
Subject: Re: [PATCH mptcp-next 0/3] mptcp: avoid data-races around the sysctls
Date: Mon, 17 Aug 2026 19:43:11 +0200	[thread overview]
Message-ID: <1a8f1b2a-df80-4257-ae67-5403f93f0a67@kernel.org> (raw)
In-Reply-To: <20260817012452.7519-1-gang.yan@linux.dev>

Hi Gang Yan,

On 17/08/2026 03:24, Gang Yan wrote:
> From: Gang Yan <yangang@kylinos.cn>
> 
> Hi,
> 
> As decribed in [1], this series is for addressing the KCSAN issues in
> sysctls.
> 
> Following the tcp_congestion_control() model, patch 1 and 2 now store
> pointers to the immutable ops and swap them atomically via xchg().
> 
> Patch 3 (from Matthieu) covers the remaining scalar sysctls with READ_ONCE().
> 
> [1] https://github.com/multipath-tcp/mptcp_net-next/issues/626

Thank you for looking at that with Tao Cui.

Globally, it looks good to me, but I have a few small requests:

- Do you mind resending this series, please: for some unknown reasons,
  Sashiko didn't get it. But before: ↓

- Can you not add Eric in Cc of the 3rd patch? Better not to spam him
for dev work → b4 send --no-trailer-to-cc ; or: git send-email
--suppress-cc=misc-by

- Could you split the code around bpf module support? I guess these
patches will be sent before adding BPF PM/sched support. In this case,
you would have squash-to patches for the BPF parts at the end of the series.

- I think you can move the WRITE_ONCE(pernet->pm_type, pm_type); from
  current patch 2 to 3, with Tao Cui's Co-dev.

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


      parent reply	other threads:[~2026-08-17 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  1:24 [PATCH mptcp-next 0/3] mptcp: avoid data-races around the sysctls Gang Yan
2026-08-17  1:24 ` [PATCH mptcp-next 1/3] mptcp: sched: change scheduler sysctl atomically Gang Yan
2026-08-17  1:24 ` [PATCH mptcp-next 2/3] mptcp: pm: change path_manager " Gang Yan
2026-08-17  1:24 ` [PATCH mptcp-next 3/3] mptcp: use READ_ONCE() over sysctls Gang Yan
2026-08-17  2:31 ` [PATCH mptcp-next 0/3] mptcp: avoid data-races around the sysctls MPTCP CI
2026-08-17 17:43 ` 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=1a8f1b2a-df80-4257-ae67-5403f93f0a67@kernel.org \
    --to=matttbe@kernel.org \
    --cc=gang.yan@linux.dev \
    --cc=mptcp@lists.linux.dev \
    --cc=yangang@kylinos.cn \
    /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