Re: [PATCH mptcp-next v3 5/5] Squash to "mptcp: pm: init and release mptcp_pm_ops"

[gang.yan@linux.dev]

August 20, 2026 at 5:07 PM, "Matthieu Baerts" <matttbe@kernel.org mailto:matttbe@kernel.org?to=%22Matthieu%20Baerts%22%20%3Cmatttbe%40kernel.org%3E > wrote:

> Can you first check if this can happen? I thought that
> mptcp_destroy_common would first close all subflows, remove the token,
> then release everything linked to the PM → so the PM will no longer be
> called at that point for this msk, right? (I didn't check)
>

Hi Matt,

Thans for looking at this and kindly remind.
Yes, I just checked the order you described is right, but I thought it
could happen in such order:

CPU A (softirq)                                 CPU B(disconnect)
->subflow_token_join_request          
->mptcp_token_get_sock()
                                              ->mptcp_destroy_common()
                                              ->pm_ops_release
->mptcp_pm_get_local_id():
  msk->pm.ops->get_local_id()   <- NULL deref

WDYT?  And, I think the window seems too narrow, we may not see it in practice,
maybe a NULL check is enough? 

Thanks
Gang