From: keith.busch@intel.com (Keith Busch)
Subject: Need help for dead lock of nvme shutdown_lock
Date: Wed, 12 Oct 2016 09:53:39 -0400 [thread overview]
Message-ID: <20161012135339.GA11730@localhost.localdomain> (raw)
In-Reply-To: <CAEj2FWN7B5svizExg7CNq+maZaP4TrabWee2B30CwAxFDp1U2g@mail.gmail.com>
On Wed, Oct 12, 2016@05:33:01PM +0800, ??? wrote:
> 2016-10-12 17:15 GMT+08:00 Shan Hai <shan.hai at oracle.com>:
> >
> > On Wed, Oct 12, 2016@03:44:34PM +0800, ??? wrote:
> > > Dear maintainers of NVME
> > > I met a dead lock issue when I was using NVME.
> > > the shutdown_lock may cause dead lock when nvme_reset_work is working
> > > and nvme_timeout happens.
> > > I checked the latest mainline code, it seems still have such issue,
> > > please help, thank you!
> > > below is the log:
> > >
> >
> > Hi Xiaoguang,
> >
> > Would you please try the below patch?
> >
> >
> Thank you very much for the quick fix, Shan
> This can absolutely fix the dead lock issue I met.
> Will this be submitted to mainline?
NAK!
First of all, you can't complete a request while the controller still
owns it. You're risking data and/or memory corruption from doing that.
Secondly, there is no such mainline kernel that tries to disable the
controller in a softirq context. Whoever built your kernel needs to
cherry pick 287922eb, "block: defer timeouts to a workqueue".
next prev parent reply other threads:[~2016-10-12 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 7:44 Need help for dead lock of nvme shutdown_lock 陈晓光
2016-10-12 9:15 ` Shan Hai
[not found] ` <57fdff29.c6efca0a.f2af0.9897SMTPIN_ADDED_BROKEN@mx.google.com>
2016-10-12 9:33 ` 陈晓光
2016-10-12 13:53 ` Keith Busch [this message]
2016-10-13 1:19 ` 陈晓光
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=20161012135339.GA11730@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.