[PATCH net-next v4 0/2] net/rds: restrict the rdma_cm ids to IB devices

[Allison Henderson <achender@kernel.org>]

Hi all,

This is v4 of the rdma_cm id restriction (v1 at [1], v2 at [2], v3 at
[3]).  Patch 1 is the restriction itself; patch 2 is a small follow-on
the v3 review turned up in the function patch 1 touches.

  Patch 1 restricts the listener, the per-connection id and the probe
  id to RDMA_NODE_IB_CA with rdma_restrict_node_type(), so the rdma_cm
  never installs the RDS listener on, or binds an RDS id to, a device
  RDS has no transport for.

  Patch 2 has rds_rdma_listen_init_common() print the port it actually
  bound: the IPv6 listener sits on RDS_CM_PORT, not RDS_PORT.

Changes since v3 [3]:
 - Fixes: dcdede0406d3 ("RDS: Drop stale iWARP RDMA transport") added,
   with a note that stable trees without rdma_restrict_node_type() need
   the separate handler fix rather than a backport of this one, and
   that the two patches are independent.
 - New patch 2 for the listener debug line.
 - Rebased onto current net-next.
 - The v3 notes linked the wrong message id for v2; corrected below.

Changes since v2 [2]:
 - The changelog no longer claims a handler-side rejection exists in
   this tree; it names the separate net fix for the handler and the
   a760e80e90f5 prerequisite.  The node_type half of the
   rds_ib_laddr_check_cm() test, dead once the id is restricted, is
   removed rather than described.

[1] https://lore.kernel.org/netdev/20260917074108.174262-1-achender@kernel.org/
[2] https://lore.kernel.org/netdev/20260919061042.250462-1-achender@kernel.org/
[3] https://lore.kernel.org/netdev/20260922084837.390414-1-achender@kernel.org/

Thank you,
Allison


Allison Henderson (2):
  net/rds: restrict the rdma_cm ids to IB devices
  net/rds: log the port a listener actually bound

 net/rds/ib.c             | 14 ++++++--------
 net/rds/ib_cm.c          | 12 ++++++++++++
 net/rds/rdma_transport.c | 13 ++++++++++++-
 3 files changed, 30 insertions(+), 9 deletions(-)

-- 
2.25.1