From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, fw@strlen.de, shuah@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/7] mptcp: fix inconsistent backup usage
Date: Tue, 30 Jul 2024 08:50:37 +0000 [thread overview]
Message-ID: <172232943732.24083.9277579847408417971.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240727-upstream-net-20240727-mptcp-backup-signal-v1-0-f50b31604cf1@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 27 Jul 2024 12:01:22 +0200 you wrote:
> In all the MPTCP backup related tests, the backup flag was set on one
> side, and the expected behaviour is to have both sides respecting this
> decision. That's also the "natural" way, and what the users seem to
> expect.
>
> On the scheduler side, only the 'backup' field was checked, which is
> supposed to be set only if the other peer flagged a subflow as backup.
> But in various places, this flag was also set when the local host
> flagged the subflow as backup, certainly to have the expected behaviour
> mentioned above.
>
> [...]
Here is the summary with links:
- [net,1/7] mptcp: sched: check both directions for backup
https://git.kernel.org/netdev/net/c/b6a66e521a20
- [net,2/7] mptcp: distinguish rcv vs sent backup flag in requests
https://git.kernel.org/netdev/net/c/efd340bf3d77
- [net,3/7] mptcp: pm: only set request_bkup flag when sending MP_PRIO
https://git.kernel.org/netdev/net/c/4258b94831bb
- [net,4/7] mptcp: mib: count MPJ with backup flag
https://git.kernel.org/netdev/net/c/4dde0d72ccec
- [net,5/7] selftests: mptcp: join: validate backup in MPJ
https://git.kernel.org/netdev/net/c/935ff5bb8a1c
- [net,6/7] mptcp: pm: fix backup support in signal endpoints
https://git.kernel.org/netdev/net/c/6834097fc38c
- [net,7/7] selftests: mptcp: join: check backup support in signal endp
https://git.kernel.org/netdev/net/c/f833470c2783
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-30 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 10:01 [PATCH net 0/7] mptcp: fix inconsistent backup usage Matthieu Baerts (NGI0)
2024-07-27 10:01 ` [PATCH net 1/7] mptcp: sched: check both directions for backup Matthieu Baerts (NGI0)
2024-07-30 8:50 ` patchwork-bot+netdevbpf [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=172232943732.24083.9277579847408417971.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=geliang@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=matttbe@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).