netdev - Re: [PATCH mlx5-next 0/5] mlx5-next updates 2022-07-03

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]

Date:   Tue, 19 Jul 2022 20:54:03 +0300
From:   Leon Romanovsky <leon@...nel.org>
To:     Saeed Mahameed <saeed@...nel.org>
Cc:     Saeed Mahameed <saeedm@...dia.com>,
        Jason Gunthorpe <jgg@...dia.com>, netdev@...r.kernel.org,
        linux-rdma@...r.kernel.org
Subject: Re: [PATCH mlx5-next 0/5] mlx5-next updates 2022-07-03

On Sun, Jul 03, 2022 at 01:54:02PM -0700, Saeed Mahameed wrote:
> From: Saeed Mahameed <saeedm@...dia.com>
> 
> Mark Bloch Says:
> ================
> Expose steering anchor
> 
> Expose a steering anchor per priority to allow users to re-inject
> packets back into default NIC pipeline for additional processing.
> 
> MLX5_IB_METHOD_STEERING_ANCHOR_CREATE returns a flow table ID which
> a user can use to re-inject packets at a specific priority.
> 
> A FTE (flow table entry) can be created and the flow table ID
> used as a destination.
> 
> When a packet is taken into a RDMA-controlled steering domain (like
> software steering) there may be a need to insert the packet back into
> the default NIC pipeline. This exposes a flow table ID to the user that can
> be used as a destination in a flow table entry.
> 
> With this new method priorities that are exposed to users via
> MLX5_IB_METHOD_FLOW_MATCHER_CREATE can be reached from a non-zero UID.
> 
> As user-created flow tables (via RDMA DEVX) are created with a non-zero UID
> thus it's impossible to point to a NIC core flow table (core driver flow tables
> are created with UID value of zero) from userspace.
> Create flow tables that are exposed to users with the shared UID, this
> allows users to point to default NIC flow tables.
> 
> Steering loops are prevented at FW level as FW enforces that no flow
> table at level X can point to a table at level lower than X. 
> 
> ===============
> 
> Mark Bloch (5):
>   net/mlx5: Expose the ability to point to any UID from shared UID
>   net/mlx5: fs, expose flow table ID to users
>   net/mlx5: fs, allow flow table creation with a UID
>   RDMA/mlx5: Refactor get flow table function
>   RDMA/mlx5: Expose steering anchor to userspace
> 

Thanks, applied.