linux-kernel - Re: [PATCH rdma-next v5 0/3] Track memory allocation with restrack DB help (Part II)

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: <20201127160345.GA667848@nvidia.com>
Date:   Fri, 27 Nov 2020 12:03:45 -0400
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Leon Romanovsky <leon@...nel.org>
CC:     Doug Ledford <dledford@...hat.com>,
        Leon Romanovsky <leonro@...dia.com>,
        Ariel Levkovich <lariel@...lanox.com>,
        Gal Pressman <galpress@...zon.com>,
        Leon Romanovsky <leonro@...lanox.com>,
        <linux-kernel@...r.kernel.org>, <linux-rdma@...r.kernel.org>,
        Mark Zhang <markz@...dia.com>,
        Yishai Hadas <yishaih@...dia.com>
Subject: Re: [PATCH rdma-next v5 0/3] Track memory allocation with restrack
 DB help (Part II)

On Tue, Nov 17, 2020 at 09:01:45AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.com>
> 
> Changelog:
> v5:
>  * Reorder patches to postpone changes in rdma_restrack_add to be in next series.
> v4: https://lore.kernel.org/linux-rdma/20201104144008.3808124-1-leon@kernel.org/
>  * Rebased on latest for-upstream, all that time the patches were in
>  our regression and didn't introduce any issues.
>  * Took first five patches that hadn't any comments
> v3: https://lore.kernel.org/lkml/20200926101938.2964394-1-leon@kernel.org
>  * Rebased on already accepted patches.
>  * Added mlx4 special QPs to the list of not-tracked QPs (dropped previous mlx4 special QP patch).
>  * Separated to two patches change in return value of cma_listen_* routines.
>  * Changed commit messages and added Fixes as Jason requested.
> v2: https://lore.kernel.org/linux-rdma/20200907122156.478360-1-leon@kernel.org/
>  * Added new patch to fix mlx4 failure on SR-IOV, it didn't have port set.
>  * Changed "RDMA/cma: Delete from restrack DB after successful destroy" patch.
> v1: https://lore.kernel.org/lkml/20200830101436.108487-1-leon@kernel.org
>  * Fixed rebase error, deleted second assignment of qp_type.
>  * Rebased code on latests rdma-next, the changes in cma.c caused to change
>    in patch "RDMA/cma: Delete from restrack DB after successful destroy".
>  * Dropped patch of port assignment, it is already done as part of this
>    series.
>  * I didn't add @calller description, regular users should not use _named() funciton.
> v0: https://lore.kernel.org/lkml/20200824104415.1090901-1-leon@kernel.org
> 
> ----------------------------------------------------------------------------------
> 
> Leon Romanovsky (3):
>   RDMA/core: Track device memory MRs
>   RDMA/core: Allow drivers to disable restrack DB
>   RDMA/restrack: Support all QP types

Applied to for-next, thanks

Jason