public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Allison Henderson <achender@kernel.org>
To: Weiming Shi <bestswngs@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org,  linux-rdma@vger.kernel.org,
	Xiang Mei <xmei5@asu.edu>
Subject: Re: [PATCH net] rds: ib: reject FRMR registration before IB connection is established
Date: Wed, 01 Apr 2026 17:36:53 -0700	[thread overview]
Message-ID: <b34739e6a4ac19fe4d8f361177056e3bdb30fa71.camel@kernel.org> (raw)
In-Reply-To: <20260330163237.2752440-2-bestswngs@gmail.com>

On Tue, 2026-03-31 at 00:32 +0800, Weiming Shi wrote:
> rds_ib_get_mr() extracts the rds_ib_connection from conn->c_transport_data
> and passes it to rds_ib_reg_frmr() for FRWR memory registration. On a
> fresh outgoing connection, ic is allocated in rds_ib_conn_alloc() with
> i_cm_id = NULL because the connection worker has not yet called
> rds_ib_conn_path_connect() to create the rdma_cm_id. When sendmsg() with
> RDS_CMSG_RDMA_MAP is called on such a connection, the sendmsg path parses
> the control message before any connection establishment, allowing
> rds_ib_post_reg_frmr() to dereference ic->i_cm_id->qp and crash the
> kernel.
> 
> The existing guard in rds_ib_reg_frmr() only checks for !ic (added in
> commit 9e630bcb7701), which does not catch this case since ic is allocated
> early and is always non-NULL once the connection object exists.
> 
>  KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
>  RIP: 0010:rds_ib_post_reg_frmr+0x50e/0x920
>  Call Trace:
>   rds_ib_post_reg_frmr (net/rds/ib_frmr.c:167)
>   rds_ib_map_frmr (net/rds/ib_frmr.c:252)
>   rds_ib_reg_frmr (net/rds/ib_frmr.c:430)
>   rds_ib_get_mr (net/rds/ib_rdma.c:615)
>   __rds_rdma_map (net/rds/rdma.c:295)
>   rds_cmsg_rdma_map (net/rds/rdma.c:860)
>   rds_sendmsg (net/rds/send.c:1363)
>   ____sys_sendmsg
>   do_syscall_64
> 
> Add a check in rds_ib_get_mr() that verifies ic, i_cm_id, and qp are all
> non-NULL before proceeding with FRMR registration, mirroring the guard
> already present in rds_ib_post_inv(). Return -ENODEV when the connection
> is not ready, which the existing error handling in rds_cmsg_send() converts
> to -EAGAIN for userspace retry and triggers rds_conn_connect_if_down() to
> start the connection worker.
> 
> Fixes: 1659185fb4d0 ("RDS: IB: Support Fastreg MR (FRMR) memory registration mode")
> Reported-by: Xiang Mei <xmei5@asu.edu>
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> ---
>  net/rds/ib_rdma.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/net/rds/ib_rdma.c b/net/rds/ib_rdma.c
> index 077f7041df155..2cfec252eeac2 100644
> --- a/net/rds/ib_rdma.c
> +++ b/net/rds/ib_rdma.c
> @@ -604,8 +604,13 @@ void *rds_ib_get_mr(struct scatterlist *sg, unsigned long nents,
>  		return ibmr;
>  	}
>  
> -	if (conn)
> +	if (conn) {
>  		ic = conn->c_transport_data;
> +		if (!ic || !ic->i_cm_id || !ic->i_cm_id->qp) {
> +			ret = -ENODEV;
> +			goto out;
> +		}
> +	}
>  
>  	if (!rds_ibdev->mr_8k_pool || !rds_ibdev->mr_1m_pool) {
>  		ret = -ENODEV;

Hi Weiming,

Apologies for the delay, this looks looks fine to me.  Thanks for catching this.

Reviewed-by: Allison Henderson <achender@kernel.org>


  parent reply	other threads:[~2026-04-02  0:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 16:32 [PATCH net] rds: ib: reject FRMR registration before IB connection is established Weiming Shi
2026-04-01  2:26 ` Jakub Kicinski
2026-04-02  0:36 ` Allison Henderson [this message]
2026-04-02  2:00 ` patchwork-bot+netdevbpf

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=b34739e6a4ac19fe4d8f361177056e3bdb30fa71.camel@kernel.org \
    --to=achender@kernel.org \
    --cc=bestswngs@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=xmei5@asu.edu \
    /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