From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, Zhang Yi <yizhan@redhat.com>,
linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Subject: [PATCH 0/2] nvme: fix hang in path of removing disk
Date: Wed, 17 May 2017 09:27:27 +0800 [thread overview]
Message-ID: <20170517012729.13469-1-ming.lei@redhat.com> (raw)
The 1st patch fixes one race between resettting failure and remove.
The 2nd patch avoids hanging in del_gendisk() if del_gendisk() waits
for these submitted writeback requests.
Keith, about the 1st patch, as we talked, there are two directions for
fixing the 1st issue, I know you may be working towards treating this
reset failure as controller dead, and not completed yet. But if
nvme_remove_dead_ctrl() is needed in any one of reset failure path,
this patch is still required. Seems both two directions aren't
contradictorily.
Ming Lei (2):
nvme: fix race between removing and reseting failure
nvme: avoid to hang in remove disk
drivers/nvme/host/core.c | 8 ++++++++
drivers/nvme/host/pci.c | 9 ++++++++-
2 files changed, 16 insertions(+), 1 deletion(-)
--
2.9.3
next reply other threads:[~2017-05-17 1:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 1:27 Ming Lei [this message]
2017-05-17 1:27 ` [PATCH 1/2] nvme: fix race between removing and reseting failure Ming Lei
2017-05-17 6:38 ` Johannes Thumshirn
2017-05-17 7:01 ` Ming Lei
2017-05-18 13:47 ` Christoph Hellwig
2017-05-18 15:04 ` Ming Lei
2017-05-18 14:13 ` Keith Busch
2017-05-19 12:52 ` Ming Lei
2017-05-19 15:15 ` Keith Busch
2017-05-19 14:41 ` Jens Axboe
2017-05-19 15:10 ` Ming Lei
2017-05-19 16:40 ` Ming Lei
2017-05-19 16:55 ` yizhan
2017-05-17 1:27 ` [PATCH 2/2] nvme: avoid to hang in remove disk Ming Lei
2017-05-18 13:49 ` Christoph Hellwig
2017-05-18 15:35 ` Ming Lei
2017-05-18 16:06 ` Keith Busch
2017-05-19 13:19 ` Ming Lei
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=20170517012729.13469-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yizhan@redhat.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;
as well as URLs for NNTP newsgroup(s).