linux-kernel - Re: [PATCH] bonding: don't force LACPDU tx to ~333 ms boundaries

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: 
 <175154940611.1481668.18355488754972268861.git-patchwork-notify@kernel.org>
Date: Thu, 03 Jul 2025 13:30:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Seth Forshee (DigitalOcean) <sforshee@...nel.org>
Cc: jv@...sburgh.net, andrew+netdev@...n.ch, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
 carlos.bilbao@...nel.org, tonghao@...aicloud.com
Subject: Re: [PATCH] bonding: don't force LACPDU tx to ~333 ms boundaries

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:

On Wed, 25 Jun 2025 11:01:24 -0500 you wrote:
> The timer which ensures that no more than 3 LACPDUs are transmitted in
> a second rearms itself every 333ms regardless of whether an LACPDU is
> transmitted when the timer expires. This causes LACPDU tx to be delayed
> until the next expiration of the timer, which effectively aligns LACPDUs
> to ~333ms boundaries. This results in a variable amount of jitter in the
> timing of periodic LACPDUs.
> 
> [...]

Here is the summary with links:
  - bonding: don't force LACPDU tx to ~333 ms boundaries
    https://git.kernel.org/netdev/net-next/c/135faae63218

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