Netdev List
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Yiming Qian <yimingqian591@gmail.com>, mptcp@lists.linux.dev
Cc: martineau@kernel.org, geliang@kernel.org, stable@vger.kernel.org,
	Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net] mptcp: pm: in-kernel: fix C-flag endpoint accounting on family mismatch
Date: Mon, 12 Oct 2026 11:40:26 +0200	[thread overview]
Message-ID: <100decff-fc86-4e82-9bb0-c22002979da7@kernel.org> (raw)
In-Reply-To: <97c651a1-7647-4f12-8b6b-74b949dce575@kernel.org>

Hi Yiming Qian,

On 06/10/2026 13:59, Matthieu Baerts wrote:
> Hi Yiming Qian,
> 
> On 06/10/2026 13:42, Yiming Qian wrote:
>> fill_local_addresses_vec_c_flag() clears the endpoint ID bit in
>> id_avail_bitmap before checking whether the endpoint's address family
>> matches the remote ADD_ADDR.  If it does not match, the loop skips the
>> endpoint without incrementing local_addr_used, leaving id_avail_bitmap
>> and local_addr_used inconsistent.
>>
>> Removing that SUBFLOW endpoint later calls
>> __mark_subflow_endp_available(), which sees the cleared bit, expects
>> local_addr_used to be non-zero, and triggers a WARN and, with
>> panic_on_warn=1, a panic.
>>
>> Keep the endpoints that are skipped during this specific C-flag
>> iteration available by tracking them in a local bitmap passed to
>> select_local_address(), instead of clearing their IDs in the per-socket
>> bitmap.  Only IDs of endpoints actually used for a subflow are now
>> cleared and accounted for.
> 
> Thank you for the patch.

Just to avoid a deadlock, do you plan to send a v2, or do you prefer if
someone else does that?

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


      reply	other threads:[~2026-10-12  9:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 11:42 [PATCH net] mptcp: pm: in-kernel: fix C-flag endpoint accounting on family mismatch Yiming Qian
2026-10-06 11:49 ` netdev-bot+sinfo
2026-10-06 11:59 ` Matthieu Baerts
2026-10-12  9:40   ` 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=100decff-fc86-4e82-9bb0-c22002979da7@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yimingqian591@gmail.com \
    /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