linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH v3 1/1] nvme: Ensure forward progress during Admin passthru
Date: Mon, 16 Jul 2018 16:09:40 -0600	[thread overview]
Message-ID: <20180716220940.GA26925@localhost.localdomain> (raw)
In-Reply-To: <20180629202350.GB13865@localhost.localdomain>

On Fri, Jun 29, 2018@02:23:50PM -0600, Keith Busch wrote:
> On Fri, Jun 29, 2018@01:03:28PM -0600, Scott Bauer wrote:
> > If the controller supports effects and goes down during
> > the passthru admin command we will deadlock during
> > namespace revalidation.
> > 
> > [  363.488275] INFO: task kworker/u16:5:231 blocked for more than 120 seconds.
> > [  363.488290]       Not tainted 4.17.0+ #2
> > [  363.488296] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > [  363.488303] kworker/u16:5   D    0   231      2 0x80000000
> > [  363.488331] Workqueue: nvme-reset-wq nvme_reset_work [nvme]
> > [  363.488338] Call Trace:
> > [  363.488385]  schedule+0x75/0x190
> > [  363.488396]  rwsem_down_read_failed+0x1c3/0x2f0
> > [  363.488481]  call_rwsem_down_read_failed+0x14/0x30
> > [  363.488504]  down_read+0x1d/0x80
> > [  363.488523]  nvme_stop_queues+0x1e/0xa0 [nvme_core]
> > [  363.488536]  nvme_dev_disable+0xae4/0x1620 [nvme]
> > [  363.488614]  nvme_reset_work+0xd1e/0x49d9 [nvme]
> > [  363.488911]  process_one_work+0x81a/0x1400
> > [  363.488934]  worker_thread+0x87/0xe80
> > [  363.488955]  kthread+0x2db/0x390
> > [  363.488977]  ret_from_fork+0x35/0x40
> > 
> > Fixes: 84fef62d135b6 ("nvme: check admin passthru command effects")
> > 
> > Signed-off-by: Scott Bauer <scott.bauer at intel.com>
> 
> Looks good to me.
> 
> Reviewed-by: Keith Busch <keith.busch at linux.intel.com>

Christoph,
Could we get this one queued up for next?

  reply	other threads:[~2018-07-16 22:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 19:59 [PATCH 0/1] nvme: Ensure forward progress during Admin passthru Scott Bauer
2018-06-22 19:59 ` [PATCH 1/1] " Scott Bauer
2018-06-27 19:12   ` Keith Busch
2018-06-27 19:01     ` Scott Bauer
2018-06-27 20:27       ` Keith Busch
2018-06-27 20:49         ` Keith Busch
2018-06-24 17:38 ` [PATCH 0/1] " Sagi Grimberg
2018-06-27 19:08   ` Keith Busch
2018-06-28 17:10 ` [PATCH v2 1/1] " Scott Bauer
2018-06-28 19:16   ` Keith Busch
2018-06-28 19:19     ` Scott Bauer
2018-06-28 19:54       ` Keith Busch
2018-06-29 19:03 ` [PATCH v3 " Scott Bauer
2018-06-29 20:23   ` Keith Busch
2018-07-16 22:09     ` Keith Busch [this message]
2018-07-17 12:42       ` Christoph Hellwig
2018-07-18 11:26         ` 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=20180716220940.GA26925@localhost.localdomain \
    --to=keith.busch@linux.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 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).