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: <165354181276.23912.16447373310059489.git-patchwork-notify@kernel.org>
Date:   Thu, 26 May 2022 05:10:12 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Daniel Borkmann <daniel@...earbox.net>
Cc:     kuba@...nel.org, wangyuweihx@...il.com, pabeni@...hat.com,
        netdev@...r.kernel.org, razor@...ckwall.org
Subject: Re: [PATCH net] net, neigh: Set lower cap for neigh_managed_work rearming

Hello:

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

On Wed, 25 May 2022 00:56:18 +0200 you wrote:
> Yuwei reported that plain reuse of DELAY_PROBE_TIME to rearm work queue
> in neigh_managed_work is problematic if user explicitly configures the
> DELAY_PROBE_TIME to 0 for a neighbor table. Such misconfig can then hog
> CPU to 100% processing the system work queue. Instead, set lower interval
> bound to HZ which is totally sufficient. Yuwei is additionally looking
> into making the interval separately configurable from DELAY_PROBE_TIME.
> 
> [...]

Here is the summary with links:
  - [net] net, neigh: Set lower cap for neigh_managed_work rearming
    https://git.kernel.org/netdev/net/c/ed6cd6a17896

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