linux-kernel - Re: [PATCH rdma-next v1] RDMA/core: Initialize lock when allocate a rdma_hw

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: <20211027164016.GA631278@nvidia.com>
Date:   Wed, 27 Oct 2021 13:40:16 -0300
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Leon Romanovsky <leon@...nel.org>
Cc:     Doug Ledford <dledford@...hat.com>,
        Mark Zhang <markzhang@...dia.com>,
        linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
        Maor Gottlieb <maorg@...dia.com>
Subject: Re: [PATCH rdma-next v1] RDMA/core: Initialize lock when allocate a
 rdma_hw_stats structure

On Tue, Oct 26, 2021 at 11:43:03AM +0300, Leon Romanovsky wrote:
> From: Mark Zhang <markzhang@...dia.com>
> 
> Initialize the rdma_hw_stats "lock" field when do allocation, to fix the
> warning below. Then we don't need to initialize it in sysfs, remove it.

>  drivers/infiniband/core/sysfs.c | 2 --
>  drivers/infiniband/core/verbs.c | 1 +
>  2 files changed, 1 insertion(+), 2 deletions(-)

Applied to for-next

Jason