From: Serhat Kumral <serhatkumral1@gmail.com>
To: yanjun.zhu@linux.dev
Cc: dsahern@kernel.org, jgg@ziepe.ca, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
serhatkumral1@gmail.com,
syzbot+8c9eede336e3a843750e@syzkaller.appspotmail.com,
zyjzyj2000@gmail.com
Subject: Re: [PATCH v3] RDMA/rxe: rework per-net tunnel socket lifetime to fix refcount underflow
Date: Wed, 8 Jul 2026 21:10:07 +0300 [thread overview]
Message-ID: <20260708181007.24280-1-serhatkumral1@gmail.com> (raw)
In-Reply-To: <6ced0145-30ab-4af5-9005-9da024933fff@linux.dev>
Hi Yanjun,
> However, after the network namespace teardown, the associated netdevice
> is still unregistered, which
> triggers the NETDEV_UNREGISTER notifier. In rxe_notify(), this event
> eventually calls rxe_net_del() to
> remove the RDMA link.
Isn't the ordering the other way around? The netdevices of a dying
netns are unregistered by default_device_exit_batch(), a pernet
device op, while rxe_net_ops is a pernet subsys, and subsys exits
run after all device exits. So NETDEV_UNREGISTER (and the notifier's
rxe_net_del()) should have already completed before rxe_ns_exit()
destroys the mutex.
Am I missing a path where rxe_net_del() can run after rxe_ns_exit()?
Thanks,
Serhat
next prev parent reply other threads:[~2026-07-08 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 16:00 [PATCH v3] RDMA/rxe: rework per-net tunnel socket lifetime to fix refcount underflow Serhat Kumral
2026-07-07 23:16 ` Yanjun.Zhu
2026-07-08 18:10 ` Serhat Kumral [this message]
2026-07-09 3:33 ` Zhu Yanjun
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=20260708181007.24280-1-serhatkumral1@gmail.com \
--to=serhatkumral1@gmail.com \
--cc=dsahern@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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