From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 1/5] nvme-core: Make nvme_init/uninit_ctrl setup/teardown symmetric
Date: Wed, 18 Oct 2017 10:21:12 -0600 [thread overview]
Message-ID: <20171018162111.GA1780@localhost.localdomain> (raw)
In-Reply-To: <4627b34e-449a-cd93-ac70-a628d558cac3@grimberg.me>
On Wed, Oct 18, 2017@06:29:40PM +0300, Sagi Grimberg wrote:
> Can you explain how would I see naming clashes? I'm not sure I
> understand what you are referring to.
It's been a while since I tested this. I used to observe -EEXIST errors
setting up the kobj's from something as simple as this:
dd if=/dev/nvme0n1 of=/dev/null conv=noerror 2> /dev/null &
echo 1 > /sys/class/nvme/nvme0/device/remove
echo 1 > /sys/bus/pci/rescan
The rescan would recreate nvme0n1 that still exists from the open
handle. I'm not seeing an error today; not sure what changed, but I'm
looking into that now.
next prev parent reply other threads:[~2017-10-18 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 11:07 [PATCH 0/5] Small rework of nvme_init/uninit_ctrl Sagi Grimberg
2017-10-18 11:07 ` [PATCH 1/5] nvme-core: Make nvme_init/uninit_ctrl setup/teardown symmetric Sagi Grimberg
2017-10-18 15:08 ` Keith Busch
2017-10-18 15:29 ` Sagi Grimberg
2017-10-18 16:21 ` Keith Busch [this message]
2017-10-18 20:17 ` Keith Busch
2017-10-19 15:19 ` Sagi Grimberg
2017-10-19 15:29 ` Christoph Hellwig
2017-10-19 15:31 ` Sagi Grimberg
2017-10-22 11:11 ` Sagi Grimberg
2017-10-23 14:31 ` Christoph Hellwig
2017-10-18 11:07 ` [PATCH 2/5] nvme-rdma: rework create_ctrl error flow Sagi Grimberg
2017-10-23 14:32 ` Christoph Hellwig
2017-10-23 15:25 ` Sagi Grimberg
2017-10-18 11:07 ` [PATCH 3/5] nvme-rdma: remove redundant check if the ctrl is in the ctrl when freeing it Sagi Grimberg
2017-10-18 11:07 ` [PATCH 4/5] nvme-loop: rework create_ctrl error flow Sagi Grimberg
2017-10-18 11:07 ` [PATCH 5/5] nvme-loop: remove redundant check if the ctrl is in the ctrl when freeing it 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=20171018162111.GA1780@localhost.localdomain \
--to=keith.busch@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.