lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: 
 <172232943732.24083.9277579847408417971.git-patchwork-notify@kernel.org>
Date: Tue, 30 Jul 2024 08:50:37 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Matthieu Baerts <matttbe@...nel.org>
Cc: mptcp@...ts.linux.dev, martineau@...nel.org, geliang@...nel.org,
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 fw@...len.de, shuah@...nel.org, netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
 stable@...r.kernel.org, rostedt@...dmis.org, mhiramat@...nel.org,
 mathieu.desnoyers@...icios.com, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH net 0/7] mptcp: fix inconsistent backup usage

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@...hat.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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ