linux-kernel - Re: [PATCH net-next 0/6] Allow parallel devlink execution

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]

Date:   Mon, 6 Dec 2021 18:00:27 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Leon Romanovsky <leon@...nel.org>
Cc:     "David S . Miller" <davem@...emloft.net>,
        Leon Romanovsky <leonro@...dia.com>,
        Ido Schimmel <idosch@...dia.com>, Jiri Pirko <jiri@...dia.com>,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/6] Allow parallel devlink execution

On Sun,  5 Dec 2021 10:22:00 +0200 Leon Romanovsky wrote:
> This is final piece of devlink locking puzzle, where I remove global
> mutex lock (devlink_mutex), so we can run devlink commands in parallel.
> 
> The series starts with addition of port_list_lock, which is needed to
> prevent locking dependency between netdevsim sysfs and devlink. It
> follows by the patch that adds context aware locking primitives. Such
> primitives allow us to make sure that devlink instance is locked and
> stays locked even during reload operation. The last patches opens
> devlink to parallel commands.

I'm not okay with assuming that all sub-objects are added when devlink
is not registered.