Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Serhat Kumral <serhatkumral1@gmail.com>
Cc: yanjun.zhu@linux.dev, dsahern@kernel.org, leon@kernel.org,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	syzbot+8c9eede336e3a843750e@syzkaller.appspotmail.com,
	zyjzyj2000@gmail.com
Subject: Re: [PATCH] RDMA/rxe: rework per-net tunnel socket lifetime to fix refcount underflow
Date: Thu, 9 Jul 2026 12:48:10 -0300	[thread overview]
Message-ID: <20260709154810.GK118978@ziepe.ca> (raw)
In-Reply-To: <20260706181404.6687-1-serhatkumral1@gmail.com>

On Mon, Jul 06, 2026 at 09:14:04PM +0300, Serhat Kumral wrote:

> For that remaining window, instead of rtnl_lock() or a global mutex,
> v2 makes rxe_net_del() idempotent per device with a test_and_set_bit()
> in struct rxe_dev, so only the first invocation drops the pernet
> socket references. This keeps the serialization at device granularity
> without adding any global locking. If you would rather serialize
> dellink itself, I am happy to respin that way.

I'm not taking any bodges for this namespace stuff until it is
rewritten not to use net ns notifiers.

sockets need to be linked to GID entries and take their namespaces and
addressing from the gid entries.

This will fix all the lifetime issues.

Jason

      reply	other threads:[~2026-07-09 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04 10:25 [PATCH] RDMA/rxe: rework per-net tunnel socket lifetime to fix refcount underflow Serhat Kumral
2026-07-04 17:11 ` Zhu Yanjun
2026-07-06 18:14   ` Serhat Kumral
2026-07-09 15:48     ` 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=20260709154810.GK118978@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dsahern@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=serhatkumral1@gmail.com \
    --cc=syzbot+8c9eede336e3a843750e@syzkaller.appspotmail.com \
    --cc=yanjun.zhu@linux.dev \
    --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