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  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]
Date:   Fri, 29 May 2020 16:17:57 -0300
From:   Jason Gunthorpe <jgg@...pe.ca>
To:     linux-rdma@...r.kernel.org, netdev@...r.kernel.org
Cc:     Ariel Elior <aelior@...vell.com>, aron.silverton@...cle.com,
        Bernard Metzler <bmt@...ich.ibm.com>,
        Bart Van Assche <bvanassche@....org>,
        Dennis Dalessandro <dennis.dalessandro@...el.com>,
        Devesh Sharma <devesh.sharma@...adcom.com>,
        Faisal Latif <faisal.latif@...el.com>,
        Gal Pressman <galpress@...zon.com>,
        Israel Rukshin <israelr@...lanox.com>,
        Leon Romanovsky <leonro@...lanox.com>,
        Max Gurtovoy <maxg@...lanox.com>,
        Mike Marciniszyn <mike.marciniszyn@...el.com>,
        Michal Kalderon <mkalderon@...vell.com>, oren@...lanox.com,
        Sagi Grimberg <sagi@...mberg.me>, santosh.shilimkar@...cle.com,
        Selvin Xavier <selvin.xavier@...adcom.com>,
        Shiraz Saleem <shiraz.saleem@...el.com>, shlomin@...lanox.com,
        Somnath Kotur <somnath.kotur@...adcom.com>,
        Sriharsha Basavapatna <sriharsha.basavapatna@...adcom.com>,
        vladimirk@...lanox.com, Yishai Hadas <yishaih@...lanox.com>
Subject: Re: [PATCH v3 00/13] Remove FMR support from RDMA drivers

On Thu, May 28, 2020 at 04:45:42PM -0300, Jason Gunthorpe wrote:
> From: Jason Gunthorpe <jgg@...lanox.com>
> 
> This series removes the support for FMR mode to register memory. This
> ancient mode is unsafe (rkeys that are usually exposed for caching
> purposes and the API is limited to page granularity mappings) and not
> maintained/tested in the last few years. It also doesn't have any
> reasonable advantage over other memory registration methods such as
> FRWR (that is implemented in all the recent RDMA adapters). This series
> should be reviewed and approved by the maintainer of the effected drivers
> and I suggest to test it as well.
> 
> Changes from V2:
>  - Removed more occurances of _fmr
>  - Remove max_map_per_fmr device attribute
>  - Remove max_fmr device attribute
>  - Remove additional dead code from bnxt_re and i40iw
>  - Revised RDS to not use ib_fmr_attr or other fmr things
>  - Rebased on RDMA for-next
> Changes from V1:
>  https://lore.kernel.org/linux-rdma/20200527094634.24240-1-maxg@mellanox.com/
>  - added "RDMA/mlx5: Remove FMR leftovers" (from GalP)
>  - rebased on top of "Linux 5.7-rc7"
>  - added "Reviewed-by" Bart signature for SRP
> 
> Cc: shlomin@...lanox.com
> Cc: vladimirk@...lanox.com
> Cc: oren@...lanox.com
> 
> Gal Pressman (1):
>   RDMA/mlx5: Remove FMR leftovers
> 
> Israel Rukshin (1):
>   RDMA/iser: Remove support for FMR memory registration
> 
> Jason Gunthorpe (4):
>   RDMA/bnxt_re: Remove FMR leftovers
>   RDMA/i40iw: Remove FMR leftovers
>   RDMA: Remove 'max_fmr'
>   RDMA: Remove 'max_map_per_fmr'
> 
> Max Gurtovoy (7):
>   RDMA/srp: Remove support for FMR memory registration
>   RDMA/rds: Remove FMR support for memory registration
>   RDMA/core: Remove FMR pool API
>   RDMA/mlx4: Remove FMR support for memory registration
>   RDMA/mthca: Remove FMR support for memory registration
>   RDMA/rdmavt: Remove FMR memory registration
>   RDMA/core: Remove FMR device ops

Applied to for-next

Jason

Powered by blists - more mailing lists