netdev - Re: [net-next 15/15] net/mlx5e: Use read lock for eswitch get callbacks

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: <1b93df01-e8a7-5446-7aac-a1192f49d5bb@intel.com>
Date:   Wed, 18 Jan 2023 13:51:29 -0800
From:   Jacob Keller <jacob.e.keller@...el.com>
To:     Saeed Mahameed <saeed@...nel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Eric Dumazet <edumazet@...gle.com>
CC:     Saeed Mahameed <saeedm@...dia.com>, <netdev@...r.kernel.org>,
        Tariq Toukan <tariqt@...dia.com>,
        Leon Romanovsky <leonro@...dia.com>
Subject: Re: [net-next 15/15] net/mlx5e: Use read lock for eswitch get
 callbacks



On 1/18/2023 10:36 AM, Saeed Mahameed wrote:
> From: Leon Romanovsky <leonro@...dia.com>
> 
> In commit 367dfa121205 ("net/mlx5: Remove devl_unlock from
> mlx5_eswtich_mode_callback_enter") all functions were converted
> to use write lock without relation to their actual purpose.
> 
> Change the devlink eswitch getters to use read and not write locks.
> 
Makes sense.

Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>