MPTCP Linux Development
 help / color / mirror / Atom feed
From: Hangbin Liu <hangbin.liu@linux.dev>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 2/2] selftests: mptcp: convert iptables to nftables for mptcp_join.sh
Date: Fri, 4 Sep 2026 16:01:54 +0800	[thread overview]
Message-ID: <app68h1_rYkPBpvn@fedora> (raw)
In-Reply-To: <6c9dd599-e9d2-470f-bc7f-2af2e9d003b6@kernel.org>

On Thu, Sep 03, 2026 at 11:28:28AM +0200, Matthieu Baerts wrote:
> Hi Hangbin,
> 
> On 03/09/2026 04:02, Hangbin Liu wrote:
> > Hi Matthieu,
> > 
> > Sorry, My mbsync has some delays and I post v2 too quick before catching
> > your feedback.
> 
> No problem.
> 
> Just in case, maybe korgalore can help?
> 
> https://people.kernel.org/monsieuricon/tracking-kernel-development-with-korgalore

Thanks, learned a new tool.

> >> If you don't need this one (or any set in helpers), don't set it/them,
> >> and don't use a global variable. Or reset it in init_partial, but prefer
> >> using local variable with a limited scope.
> > 
> > Yes, we don't need the handle in other place, which I will remove them.
> > But for endpoint_tests(), after adding rules in reset_with_tcp_filter,
> > we need to remove the rule outside. I will reset it after each test.
> 
> Perhaps you could flush the whole table instead? But if it makes more
> sense to assign this variable, fine by me.

Yes, if not in purpose, I feel flush the whole table is dangerous.
Some rules may still in using in later testing.

> > Thanks for the notes. I used to rely on `b4 auto-to-cc` too much...
> 
> Most of the time, that's fine. It's just for some subsubtrees where
> (urgent & simple) fixes can go to the parent tree (netdev here)
> directly, but the rest can go only to the subsubtree ML.
> 
> BTW, if you are on top of our export(-net) (or for-review(-net)) branch,
> there is a .b4-config: you just need to use 'b4 send' then :)

Thanks. I am working on top of the export branch. I ran into a small issue
while using b4. The export branch is not fast‑forwardable. I used
`git reset --hard` to fall back to the top merge commit, then ran
`git pull` to fetch the latest changes.

However, I cannot perform a reset on the b4 branch, and git rebase also failed.
These steps have blocked me a little. I have to manually recreate the b4 branch,
or perhaps avoid using b4 when working on mptcp changes.

> 
> > An example of `nft -j` output:
> 
> Thanks for the output!

I have post the new version, which use jq to get the handle now.

Thanks
Hangbin

  reply	other threads:[~2026-09-04  8:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  6:52 [PATCH mptcp-next 0/2] selftests: mptcp: convert iptables to nftables Hangbin Liu
2026-09-02  6:52 ` [PATCH mptcp-next 1/2] selftests: mptcp: convert iptables to nftables for mptcp_sockopt.sh Hangbin Liu
2026-09-02  7:02   ` sashiko-bot
2026-09-02  7:47     ` Hangbin Liu
2026-09-02  9:17   ` Matthieu Baerts
2026-09-03  2:15     ` Hangbin Liu
2026-09-02  6:52 ` [PATCH mptcp-next 2/2] selftests: mptcp: convert iptables to nftables for mptcp_join.sh Hangbin Liu
2026-09-02 10:00   ` Matthieu Baerts
2026-09-03  2:02     ` Hangbin Liu
2026-09-03  6:35       ` Hangbin Liu
2026-09-03  6:54         ` Florian Westphal
2026-09-03  7:35           ` Hangbin Liu
2026-09-03  9:28       ` Matthieu Baerts
2026-09-04  8:01         ` Hangbin Liu [this message]
2026-09-04 16:40           ` Matthieu Baerts
2026-09-07  1:02             ` Hangbin Liu
2026-09-07  5:50               ` Matthieu Baerts
2026-09-07  6:59                 ` Hangbin Liu
2026-09-07  7:55                   ` Matthieu Baerts
2026-09-02  7:23 ` [PATCH mptcp-next 0/2] selftests: mptcp: convert iptables to nftables MPTCP CI
2026-09-02  8:14 ` MPTCP CI

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=app68h1_rYkPBpvn@fedora \
    --to=hangbin.liu@linux.dev \
    --cc=matttbe@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox