From: swise@opengridcomputing.com (Steve Wise)
Subject: nvme_rdma - leaves provider resources allocated
Date: Tue, 23 Aug 2016 11:58:56 -0500 [thread overview]
Message-ID: <014301d1fd5f$a2da7000$e88f5000$@opengridcomputing.com> (raw)
Assume an nvme_rdma host has one attached controller in RECONNECTING state, and
that controller has failed to reconnect at least once and thus is in the
delay_schedule time before retrying the connection. At that moment, there are
no cm_ids allocated for that controller because the admin queue and the io
queues have been freed. So nvme_rdma cannot get a DEVICE_REMOVAL from the
rdma_cm. This means if the underlying provider module is removed, it will be
removed with resources still allocated by nvme_rdma. For iw_cxgb4, this causes
a BUG_ON() in gen_pool_destroy() because MRs are still allocated for the
controller.
Thoughts on how to fix this?
Thanks,
Steve.
next reply other threads:[~2016-08-23 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 16:58 Steve Wise [this message]
2016-08-24 9:31 ` nvme_rdma - leaves provider resources allocated Sagi Grimberg
2016-08-24 14:09 ` Steve Wise
2016-08-25 21:52 ` Sagi Grimberg
2016-08-25 22:03 ` Steve Wise
2016-08-25 22:06 ` Sagi Grimberg
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='014301d1fd5f$a2da7000$e88f5000$@opengridcomputing.com' \
--to=swise@opengridcomputing.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