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]
Date: Thu, 04 Apr 2024 02:30:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Marcelo Tosatti <mtosatti@...hat.com>
Cc: netdev@...r.kernel.org, willemdebruijn.kernel@...il.com, kuba@...nel.org,
 edumazet@...gle.com, frederic@...nel.org, vschneid@...hat.com,
 pabeni@...hat.com
Subject: Re: [PATCH net-next -v7] net: enable timestamp static key if CPU

Hello:

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

On Mon, 1 Apr 2024 12:36:40 -0300 you wrote:
> For systems that use CPU isolation (via nohz_full), creating or destroying
> a socket with SO_TIMESTAMP, SO_TIMESTAMPNS or SO_TIMESTAMPING with flag
> SOF_TIMESTAMPING_RX_SOFTWARE will cause a static key to be enabled/disabled.
> This in turn causes undesired IPIs to isolated CPUs.
> 
> So enable the static key unconditionally, if CPU isolation is enabled,
> thus avoiding the IPIs.
> 
> [...]

Here is the summary with links:
  - [net-next,-v7] net: enable timestamp static key if CPU
    https://git.kernel.org/netdev/net-next/c/2f3c7195a702

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