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] [thread-next>] [day] [month] [year] [list]
Message-Id: 
 <174424563486.3092405.11629244278236026519.git-patchwork-notify@kernel.org>
Date: Thu, 10 Apr 2025 00:40:34 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
 pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org, sdf@...ichev.me,
 hramamurthy@...gle.com, kuniyu@...zon.com, jdamato@...tly.com
Subject: Re: [PATCH net-next v2 0/8] net: depend on instance lock for queue
 related netlink ops

Hello:

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

On Tue,  8 Apr 2025 12:59:47 -0700 you wrote:
> netdev-genl used to be protected by rtnl_lock. In previous release
> we already switched the queue management ops (for Rx zero-copy) to
> the instance lock. This series converts other ops to depend on the
> instance lock when possible.
> 
> Unfortunately queue related state is hard to lock (unlike NAPI)
> as the process of switching the number of queues usually involves
> a large reconfiguration of the driver. The reconfig process has
> historically been under rtnl_lock, but for drivers which opt into
> ops locking it is also under the instance lock. Leverage that
> and conditionally take rtnl_lock or instance lock depending
> on the device capabilities.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/8] net: avoid potential race between netdev_get_by_index_lock() and netns switch
    (no matching commit)
  - [net-next,v2,2/8] net: designate XSK pool pointers in queues as "ops protected"
    https://git.kernel.org/netdev/net-next/c/606048cbd834
  - [net-next,v2,3/8] netdev: add "ops compat locking" helpers
    (no matching commit)
  - [net-next,v2,4/8] netdev: don't hold rtnl_lock over nl queue info get when possible
    https://git.kernel.org/netdev/net-next/c/d02e3b388221
  - [net-next,v2,5/8] xdp: double protect netdev->xdp_flags with netdev->lock
    (no matching commit)
  - [net-next,v2,6/8] netdev: depend on netdev->lock for xdp features
    https://git.kernel.org/netdev/net-next/c/99e44f39a8f7
  - [net-next,v2,7/8] docs: netdev: break down the instance locking info per ops struct
    https://git.kernel.org/netdev/net-next/c/87eba404f2e1
  - [net-next,v2,8/8] netdev: depend on netdev->lock for qstats in ops locked drivers
    https://git.kernel.org/netdev/net-next/c/ce7b14947484

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