From: Leon Romanovsky <leon@kernel.org>
To: Stefan Metzmacher <metze@samba.org>
Cc: linux-rdma@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>,
Steve French <smfrench@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>, Tom Talpey <tom@talpey.com>,
Long Li <longli@microsoft.com>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org
Subject: Re: [PATCH] RDMA/core: check id_priv->restricted_node_type in cma_listen_on_dev()
Date: Wed, 25 Feb 2026 14:52:11 +0200 [thread overview]
Message-ID: <20260225125211.GE9541@unreal> (raw)
In-Reply-To: <20260224165951.3582093-2-metze@samba.org>
On Tue, Feb 24, 2026 at 05:59:52PM +0100, Stefan Metzmacher wrote:
> When listening on wildcard addresses we have a global list for
> the application layer rdma_cm_id and for any existing
> device or any device added in future we try to listen
> on any wildcard listener.
>
> When the listener has a restricted_node_type we
> should prevent listening on devices with a different
> node type.
>
> While there fix the documentation comment of
> rdma_restrict_node_type() to include rdma_resolve_addr()
> instead of having rdma_bind_addr() twice.
>
> Fixes: a760e80e90f5 ("RDMA/core: introduce rdma_restrict_node_type()")
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Leon Romanovsky <leon@kernel.org>
> Cc: Steve French <smfrench@gmail.com>
> Cc: Namjae Jeon <linkinjeon@kernel.org>
> Cc: Tom Talpey <tom@talpey.com>
> Cc: Long Li <longli@microsoft.com>
> Cc: linux-rdma@vger.kernel.org
> Cc: linux-cifs@vger.kernel.org
> Cc: samba-technical@lists.samba.org
> Signed-off-by: Stefan Metzmacher <metze@samba.org>
> ---
> drivers/infiniband/core/cma.c | 6 +++++-
> include/rdma/rdma_cm.h | 2 +-
> 2 files changed, 6 insertions(+), 2 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2026-02-25 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 16:59 [PATCH] RDMA/core: check id_priv->restricted_node_type in cma_listen_on_dev() Stefan Metzmacher
2026-02-25 12:52 ` Leon Romanovsky [this message]
2026-02-26 9:32 ` Stefan Metzmacher
2026-02-26 10:09 ` Leon Romanovsky
2026-03-02 10:33 ` Leon Romanovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260225125211.GE9541@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=metze@samba.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox