From: Geliang Tang <geliang@kernel.org>
To: Gang Yan <gang.yan@linux.dev>, mptcp@lists.linux.dev
Cc: Gang Yan <yangang@kylinos.cn>
Subject: Re: [PATCH mptcp-next v3] Squash-to "mptcp: pm: init and release mptcp_pm_ops"
Date: Fri, 03 Jul 2026 09:13:37 +0800 [thread overview]
Message-ID: <753354dacb35348baa71a80e7ee21460fa2d119f.camel@kernel.org> (raw)
In-Reply-To: <20260702063002.127027-1-gang.yan@linux.dev>
Hi Gang,
Thanks for this v3.
On Thu, 2026-07-02 at 14:30 +0800, Gang Yan wrote:
> From: Gang Yan <yangang@kylinos.cn>
>
> This patch removes the need to handle a NULL pm_ops in the fallback
> path, and moves the rcu_read_lock\unlock into mptcp_pm_ops_init.
The commit log doesn't match, but since this is a squash-to patch, it
may not be necessary to update the original commit log when merging.
Anyway, this patch LGTM. I've changed its status to "Queued".
-Geliang
>
> Following sashiko's comments, it also moves the pr_debug() before
> bpf_module_put() in mptcp_pm_ops_release.
>
> Signed-off-by: Gang Yan <yangang@kylinos.cn>
> ---
> net/mptcp/pm.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/net/mptcp/pm.c b/net/mptcp/pm.c
> index 9dc7b41fb562..033f783d4990 100644
> --- a/net/mptcp/pm.c
> +++ b/net/mptcp/pm.c
> @@ -1137,12 +1137,13 @@ void mptcp_pm_worker(struct mptcp_sock *msk)
> spin_unlock_bh(&msk->pm.lock);
> }
>
> -static void mptcp_pm_ops_init(struct mptcp_sock *msk,
> - struct mptcp_pm_ops *pm_ops)
> +static void mptcp_pm_ops_init(struct mptcp_sock *msk, const char
> *pm_name)
> {
> + struct mptcp_pm_ops *pm_ops;
> +
> + pm_ops = mptcp_pm_find(pm_name);
> if (!pm_ops || !bpf_try_module_get(pm_ops, pm_ops->owner)) {
> - pr_warn_once("pm %s fails, fallback to default pm",
> - pm_ops->name);
> + pr_warn_once("pm %s fails, fallback to default pm",
> pm_name);
> pm_ops = &mptcp_pm_kernel;
> }
>
> @@ -1161,9 +1162,9 @@ static void mptcp_pm_ops_release(struct
> mptcp_sock *msk)
> if (pm_ops->release)
> pm_ops->release(msk);
>
> - bpf_module_put(pm_ops, pm_ops->owner);
> -
> pr_debug("pm %s released\n", pm_ops->name);
> +
> + bpf_module_put(pm_ops, pm_ops->owner);
> }
>
> void mptcp_pm_destroy(struct mptcp_sock *msk)
> @@ -1185,7 +1186,7 @@ void mptcp_pm_data_reset(struct mptcp_sock
> *msk)
> WRITE_ONCE(pm->pm_type, pm_type);
>
> rcu_read_lock();
> - mptcp_pm_ops_init(msk, mptcp_pm_find(pm_name));
> + mptcp_pm_ops_init(msk, pm_name);
> rcu_read_unlock();
> }
>
next prev parent reply other threads:[~2026-07-03 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 6:30 [PATCH mptcp-next v3] Squash-to "mptcp: pm: init and release mptcp_pm_ops" Gang Yan
2026-07-02 7:35 ` MPTCP CI
2026-07-03 1:13 ` Geliang Tang [this message]
2026-07-06 14:33 ` 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=753354dacb35348baa71a80e7ee21460fa2d119f.camel@kernel.org \
--to=geliang@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