linux-kernel - Re: [PATCH net-next] mptcp: reset blackhole on success with non-loopback ifaces

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: 
 <175829222874.3219626.13984058147860089030.git-patchwork-notify@kernel.org>
Date: Fri, 19 Sep 2025 14:30:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Matthieu Baerts <matttbe@...nel.org>
Cc: martineau@...nel.org, geliang@...nel.org, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
 netdev@...r.kernel.org, mptcp@...ts.linux.dev, linux-kernel@...r.kernel.org,
 stable@...r.kernel.org, kuniyu@...gle.com
Subject: Re: [PATCH net-next] mptcp: reset blackhole on success with
 non-loopback ifaces

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Thu, 18 Sep 2025 10:50:18 +0200 you wrote:
> When a first MPTCP connection gets successfully established after a
> blackhole period, 'active_disable_times' was supposed to be reset when
> this connection was done via any non-loopback interfaces.
> 
> Unfortunately, the opposite condition was checked: only reset when the
> connection was established via a loopback interface. Fixing this by
> simply looking at the opposite.
> 
> [...]

Here is the summary with links:
  - [net-next] mptcp: reset blackhole on success with non-loopback ifaces
    https://git.kernel.org/netdev/net-next/c/833d4313bc1e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html