From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: fix nvme_ns_remove() deadlock
Date: Tue, 19 Apr 2016 11:25:17 -0700 [thread overview]
Message-ID: <20160419182517.GA19164@infradead.org> (raw)
In-Reply-To: <1461020178.1419.2.camel@ssi>
On Mon, Apr 18, 2016@03:56:18PM -0700, Ming Lin wrote:
> You mean below changes(un-tested)?
Yes, that's exactly what I had in mind.
prev parent reply other threads:[~2016-04-19 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 18:21 [PATCH] nvme: fix nvme_ns_remove() deadlock Ming Lin
2016-04-18 18:32 ` Keith Busch
2016-04-18 20:37 ` Christoph Hellwig
2016-04-18 22:56 ` Ming Lin
2016-04-19 18:25 ` Christoph Hellwig [this message]
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=20160419182517.GA19164@infradead.org \
--to=hch@infradead.org \
/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