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: <164788141087.8756.4036477791453541767.git-patchwork-notify@kernel.org>
Date:   Mon, 21 Mar 2022 16:50:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     davem@...emloft.net, netdev@...r.kernel.org, jiri@...nulli.us,
        leonro@...dia.com, saeedm@...dia.com, idosch@...sch.org,
        michael.chan@...adcom.com, simon.horman@...igine.com
Subject: Re: [PATCH net-next v2 0/5] devlink: hold the instance lock in eswitch
 callbacks

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@...emloft.net>:

On Fri, 18 Mar 2022 12:23:39 -0700 you wrote:
> Series number 2 in the effort to hold the devlink instance lock
> in call driver callbacks. We have the following drivers using
> this API:
> 
>  - bnxt, nfp, netdevsim - their own locking is removed / simplified
>    by this series; all of them needed a lock to protect from changes
>    to the number of VFs while switching modes, now the VF config bus
>    callback takes the devlink instance lock via devl_lock();
>  - ice - appears not to allow changing modes while SR-IOV enabled,
>    so nothing to do there;
>  - liquidio - does not contain any locking;
>  - octeontx2/af - is very special but at least doesn't have locking
>    so doesn't get in the way either;
>  - mlx5 has a wealth of locks - I chickened out and dropped the lock
>    in the callbacks so that I can leave the driver be, for now.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/5] bnxt: use the devlink instance lock to protect sriov
    https://git.kernel.org/netdev/net-next/c/7a1b0b1a555e
  - [net-next,v2,2/5] devlink: add explicitly locked flavor of the rate node APIs
    https://git.kernel.org/netdev/net-next/c/8879b32a3a80
  - [net-next,v2,3/5] netdevsim: replace port_list_lock with devlink instance lock
    https://git.kernel.org/netdev/net-next/c/76eea6c2e663
  - [net-next,v2,4/5] netdevsim: replace vfs_lock with devlink instance lock
    https://git.kernel.org/netdev/net-next/c/aff3a9250946
  - [net-next,v2,5/5] devlink: hold the instance lock during eswitch_mode callbacks
    https://git.kernel.org/netdev/net-next/c/14e426bf1a4d

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