linux-kernel - Re: [PATCH rdma-next 0/5] Reorganize mlx5 UMR creation flow

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: <20200918160532.GA320440@nvidia.com>
Date:   Fri, 18 Sep 2020 13:05:32 -0300
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Leon Romanovsky <leon@...nel.org>
CC:     Doug Ledford <dledford@...hat.com>,
        Leon Romanovsky <leonro@...dia.com>,
        Artemy Kovalyov <artemyko@...lanox.com>,
        <linux-kernel@...r.kernel.org>, <linux-rdma@...r.kernel.org>,
        Moni Shoua <monis@...lanox.com>,
        Yishai Hadas <yishaih@...lanox.com>
Subject: Re: [PATCH rdma-next 0/5] Reorganize mlx5 UMR creation flow

On Mon, Sep 14, 2020 at 02:26:48PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.com>
> 
> This flow has become crufty and confusing. Revise it so that the rules
> on how UMR is used with MRs is much clearer and more correct.
> 
> Fixes a few minor bugs in ODP and rereg_mr where disallowed things were
> not properly blocked.
> 
> Thanks
> 
> Jason Gunthorpe (5):
>   RDMA/mlx5: Remove dead check for EAGAIN after alloc_mr_from_cache()
>   RDMA/mlx5: Use set_mkc_access_pd_addr_fields() in reg_create()
>   RDMA/mlx5: Make mkeys always owned by the kernel's PD when not enabled
>   RDMA/mlx5: Disable IB_DEVICE_MEM_MGT_EXTENSIONS if IB_WR_REG_MR can't
>     work
>   RDMA/mlx5: Clarify what the UMR is for when creating MRs

Applied to for-next
 
Jason