Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
	Leon Romanovsky <leon@kernel.org>,
	David Ahern <dsahern@kernel.org>,
	Kuniyuki Iwashima <kuni1840@gmail.com>,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2 2/2] RDMA/rxe: Fix up RCU usage for rxe_ns_pernet_sk6().
Date: Tue, 2 Jun 2026 15:31:23 -0300	[thread overview]
Message-ID: <20260602183123.GA1045352@nvidia.com> (raw)
In-Reply-To: <20260425060436.2316620-3-kuniyu@google.com>

On Sat, Apr 25, 2026 at 06:04:14AM +0000, Kuniyuki Iwashima wrote:
> @@ -133,16 +133,21 @@ static struct dst_entry *rxe_find_route6(struct rxe_qp *qp,
>  					 struct in6_addr *saddr,
>  					 struct in6_addr *daddr)
>  {
> -	struct dst_entry *ndst;
> +	struct dst_entry *ndst = NULL;
>  	struct flowi6 fl6 = {};
> +	struct sock *sk;
>  
>  	fl6.flowi6_oif = ndev->ifindex;
>  	memcpy(&fl6.saddr, saddr, sizeof(*saddr));
>  	memcpy(&fl6.daddr, daddr, sizeof(*daddr));
>  	fl6.flowi6_proto = IPPROTO_UDP;
>  
> -	ndst = ip6_dst_lookup_flow(net, rxe_ns_pernet_sk6(net), &fl6, NULL);
> -	if (IS_ERR(ndst)) {
> +	rcu_read_lock();
> +	sk = rxe_ns_pernet_sk6(net);
> +	if (sk)
> +		ndst = ip6_dst_lookup_flow(net, sk, &fl6, NULL);
> +	rcu_read_unlock();
> +	if (IS_ERR_OR_NULL(ndst)) {
>  		rxe_dbg_qp(qp, "no route to %pI6\n", daddr);
>  		return NULL;
>  	}

This idea seems correct, but ..

>  struct sock *rxe_ns_pernet_sk6(struct net *net)
>  {
>  	struct rxe_ns_sock *ns_sk = net_generic(net, rxe_pernet_id);
> -	struct sock *sk;
> -
> -	rcu_read_lock();
> -	sk = rcu_dereference(ns_sk->rxe_sk6);
> -	rcu_read_unlock();
>
> -	return sk;
> +	return rcu_dereference(ns_sk->rxe_sk6);
>  }

This is called from several places that don't hold the rcu so it can't
quite work like this.

Jason

      parent reply	other threads:[~2026-06-02 18:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25  6:04 [PATCH v2 0/2] RDMA/rxe: Fix per-netns UDP tunnel issues Kuniyuki Iwashima
2026-04-25  6:04 ` [PATCH v2 1/2] RDMA/rxe: Fix null-ptr-deref in kernel_sock_shutdown() Kuniyuki Iwashima
2026-04-25 15:47   ` David Ahern
2026-04-25 20:55     ` Kuniyuki Iwashima
2026-04-26 16:40       ` David Ahern
2026-04-25 21:25   ` Zhu Yanjun
2026-04-26 16:42     ` David Ahern
2026-04-27  2:57       ` Zhu Yanjun
2026-04-27  3:10         ` Kuniyuki Iwashima
2026-04-27  3:53           ` Zhu Yanjun
2026-04-27 14:38             ` David Ahern
2026-04-27 20:20               ` yanjun.zhu
2026-04-28  0:52                 ` Kuniyuki Iwashima
2026-04-28  0:58                   ` David Ahern
2026-04-28  2:15                     ` Zhu Yanjun
2026-04-28  5:12                       ` Zhu Yanjun
2026-04-28  5:22                         ` Kuniyuki Iwashima
2026-04-28  6:30                           ` Zhu Yanjun
2026-04-28  6:39                             ` Kuniyuki Iwashima
2026-04-28 16:56                               ` yanjun.zhu
2026-04-25  6:04 ` [PATCH v2 2/2] RDMA/rxe: Fix up RCU usage for rxe_ns_pernet_sk6() Kuniyuki Iwashima
2026-04-25 21:26   ` Zhu Yanjun
2026-06-02 18:31   ` Jason Gunthorpe [this message]

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=20260602183123.GA1045352@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dsahern@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=zyjzyj2000@gmail.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