netdev - Re: [PATCH v3 03/13] RDMA/rds: Remove FMR support for memory registration

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: <18e8c383-ceaa-a860-4a1c-2c92cfdd3c5a@oracle.com>
Date:   Mon, 15 Jun 2020 19:33:25 -0700
From:   santosh.shilimkar@...cle.com
To:     Jason Gunthorpe <jgg@...pe.ca>
Cc:     linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
        aron.silverton@...cle.com, Max Gurtovoy <maxg@...lanox.com>,
        oren@...lanox.com, shlomin@...lanox.com, vladimirk@...lanox.com
Subject: Re: [PATCH v3 03/13] RDMA/rds: Remove FMR support for memory
 registration

On 5/29/20 12:12 PM, Jason Gunthorpe wrote:
> On Thu, May 28, 2020 at 01:21:33PM -0700, santosh.shilimkar@...cle.com wrote:
>> On 5/28/20 12:45 PM, Jason Gunthorpe wrote:
>>> From: Max Gurtovoy <maxg@...lanox.com>
>>>
>>> Use FRWR method for memory registration by default and remove the ancient
>>> and unsafe FMR method.
>>>
>>> Signed-off-by: Max Gurtovoy <maxg@...lanox.com>
>>> Signed-off-by: Jason Gunthorpe <jgg@...lanox.com>
>>
>>>    net/rds/Makefile  |   2 +-
>>>    net/rds/ib.c      |  20 ++--
>>>    net/rds/ib.h      |   2 -
>>>    net/rds/ib_cm.c   |   4 +-
>>>    net/rds/ib_fmr.c  | 269 ----------------------------------------------
>>>    net/rds/ib_frmr.c |   4 +-
>>>    net/rds/ib_mr.h   |  14 +--
>>>    net/rds/ib_rdma.c |  28 ++---
>>>    8 files changed, 21 insertions(+), 322 deletions(-)
>>>    delete mode 100644 net/rds/ib_fmr.c
>>>
>> Patch looks accurate to me Jason/Max. I wanted to get few regression
>> tests run with it before providing the ack. Will send a note once
>> its tested ok.
> 
> Okay, since we are at the merge window I'm going to put it in
> linux-next to look for build regressions with the idea to send it on
> Thursday
> 
I know you sent this to net-next already but just to close the loop, 
regression testing went ok.

Regards,
Santosh