From: Matthieu Baerts <matttbe@kernel.org>
To: hangbin.liu@linux.dev, MPTCP Linux <mptcp@lists.linux.dev>
Cc: Florian Westphal <fw@strlen.de>, Hangbin Liu <liuhangbin@kylinos.cn>
Subject: Re: [PATCH mptcp-next] selftests: mptcp: use offset to match RM_ADDR message
Date: Thu, 8 Oct 2026 15:43:03 +0200 [thread overview]
Message-ID: <e9902aae-a602-4731-84b2-0562e82a345c@kernel.org> (raw)
In-Reply-To: <a07411464cafcb016436eb3c17ffca73730d7fe1@linux.dev>
On 08/10/2026 15:40, hangbin.liu@linux.dev wrote:
(...)
> BTW, For mptcp_sockopt.sh,
>
> # just to debug: check we have multiple subflows connection requests
> add rule $table filter OUTPUT \
> tcp flags & (fin | syn | rst | ack) == syn \
> meta mark $m accept
>
> do you think if there is a need to add counter or remove this rule?
Easier to remove it. It can be easily added when debugging.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-10-08 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 10:06 [PATCH mptcp-next] selftests: mptcp: use offset to match RM_ADDR message Hangbin Liu
2026-10-08 11:21 ` MPTCP CI
2026-10-08 11:46 ` Matthieu Baerts
2026-10-08 13:40 ` hangbin.liu
2026-10-08 13: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=e9902aae-a602-4731-84b2-0562e82a345c@kernel.org \
--to=matttbe@kernel.org \
--cc=fw@strlen.de \
--cc=hangbin.liu@linux.dev \
--cc=liuhangbin@kylinos.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.