From: Jason Gunthorpe <jgg@ziepe.ca>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Bernard Metzler <bmt@zurich.ibm.com>,
Leon Romanovsky <leon@kernel.org>,
Ursula Braun <ubraun@linux.ibm.com>,
OFED mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] RDMA: don't ignore client->add() failures
Date: Thu, 30 Mar 2023 20:39:15 -0300 [thread overview]
Message-ID: <ZCYdo8pcS947JOgI@ziepe.ca> (raw)
In-Reply-To: <9186f5f5-2f88-1247-2d24-61d090a1da83@I-love.SAKURA.ne.jp>
On Thu, Mar 30, 2023 at 08:51:44AM +0900, Tetsuo Handa wrote:
> On 2023/03/30 0:44, Jason Gunthorpe wrote:
> >> The caller of ib_register_device() (i.e. siw_device_register() from
> >> siw_newlink()) is assuming that somebody will call __ib_unregister_device(),
> >> but nobody is calling __ib_unregister_device().
> >
> > On the success path this stuff happens during dellink
> >
>
> "struct rdma_link_ops" has "newlink" callback but does not have "dellink" callback.
> "struct rtnl_link_ops" has both "newlink" callback and "dellink" callback, but
> only ipoib_netlink.c defines it inside drivers/infiniband/ directory.
>
> Where is the dellink you are talking about?
> I'm not familiar with rdma code. Please explain using specific function/symbol names.
Your test code deletes a vlan
If SIW is attached to a vlan then SIW will destroy itself based on a
net notifier
Look at siw_netdev_event:
case NETDEV_UNREGISTER:
ib_unregister_device_queued(&sdev->base_dev);
break;
Jason
next prev parent reply other threads:[~2023-03-30 23:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 10:52 [PATCH] RDMA: don't ignore client->add() failures Tetsuo Handa
2023-03-28 11:24 ` Jason Gunthorpe
2023-03-28 11:33 ` Tetsuo Handa
2023-03-28 11:34 ` Jason Gunthorpe
2023-03-28 14:59 ` Tetsuo Handa
2023-03-28 16:18 ` Jason Gunthorpe
2023-03-28 22:17 ` Tetsuo Handa
2023-03-29 15:44 ` Jason Gunthorpe
2023-03-29 23:51 ` Tetsuo Handa
2023-03-30 23:39 ` Jason Gunthorpe [this message]
2023-03-31 16:19 ` Tetsuo Handa
2023-03-31 16:23 ` Jason Gunthorpe
2023-04-01 7:30 ` Tetsuo Handa
2023-04-01 18:30 ` 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=ZCYdo8pcS947JOgI@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bmt@zurich.ibm.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=ubraun@linux.ibm.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