From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH mptcp-next 0/7] mptcp: address stall under memory pressure
Date: Thu, 06 Aug 2026 17:16:39 +0800 [thread overview]
Message-ID: <355f231057ea5c58415d67efa6fde6ab5bef36ca.camel@kernel.org> (raw)
In-Reply-To: <53bf5917-392d-34b4-a12a-3e5d0ac31d29@gmail.com>
On Wed, 2026-08-05 at 17:30 +0000, MPTCP CI wrote:
> Hi Paolo,
>
> Thank you for your modifications, that's great!
>
> Our CI did some validations and here is its report:
>
> - KVM Validation: normal (except selftest_mptcp_join): Success! ✅
> - KVM Validation: normal (only selftest_mptcp_join): Success! ✅
> - KVM Validation: debug (except selftest_mptcp_join): Success! ✅
> - KVM Validation: debug (only selftest_mptcp_join): Success! ✅
> - KVM Validation: btf-normal (only bpftest_all): Unstable: 3 failed
> test(s): bpftest_test_progs-cpuv4_mptcp bpftest_test_progs-
> no_alu32_mptcp bpftest_test_progs_mptcp ⚠️
Since mptcp_pm_subflow_chk_stale is removed in this series, it also
needs to be removed from BPF to keep the BPF tests passing. I just sent
two squash-to patches to fix this.
Thanks,
-Geliang
> - KVM Validation: btf-debug (only bpftest_all): Success! ✅
> - Task:
> https://github.com/multipath-tcp/mptcp_net-next/actions/runs/31026237379
>
> Initiator: Patchew Applier
> Commits:
> https://github.com/multipath-tcp/mptcp_net-next/commits/503660467176
> Patchwork:
> https://patchwork.kernel.org/project/mptcp/list/?series=1140906
>
>
> If there are some issues, you can reproduce them using the same
> environment as
> the one used by the CI thanks to a docker image, e.g.:
>
> $ cd [kernel source code]
> $ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm
> -it \
> --pull always mptcp/mptcp-upstream-virtme-docker:latest \
> auto-normal
>
> For more details:
>
> https://github.com/multipath-tcp/mptcp-upstream-virtme-docker
>
>
> Please note that despite all the efforts that have been already done
> to have a
> stable tests suite when executed on a public CI like here, it is
> possible some
> reported issues are not due to your modifications. Still, do not
> hesitate to
> help us improve that ;-)
>
> Cheers,
> MPTCP GH Action bot
> Bot operated by Matthieu Baerts (NGI0 Core)
prev parent reply other threads:[~2026-08-06 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 15:52 [PATCH mptcp-next 0/7] mptcp: address stall under memory pressure Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 1/7] mptcp: move the retrans loop to a separate helper Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 2/7] mptcp: move the stale logic out of retrans scheduler Paolo Abeni
2026-08-06 9:31 ` Geliang Tang
2026-08-06 16:57 ` Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 3/7] mptcp: let the retrans scheduler do its job Paolo Abeni
2026-08-06 7:39 ` Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 4/7] mptcp: explicitly drop over memory limits Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 5/7] mptcp: enforce hard limit on backlog flushing Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 6/7] mptcp: avoid code duplication in __mptcp_move_skb() Paolo Abeni
2026-08-05 16:17 ` [PATCH mptcp-next 7/7] mptcp: implemented OoO queue pruning Paolo Abeni
2026-08-05 17:30 ` [PATCH mptcp-next 0/7] mptcp: address stall under memory pressure MPTCP CI
2026-08-06 9:16 ` Geliang Tang [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=355f231057ea5c58415d67efa6fde6ab5bef36ca.camel@kernel.org \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.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 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.