From: hch@infradead.org (Christoph Hellwig)
Subject: [REPOST PATCH] nvmet: Fix fatal_err_work deadlock
Date: Fri, 20 Oct 2017 03:27:21 -0700 [thread overview]
Message-ID: <20171020102721.GA20587@infradead.org> (raw)
In-Reply-To: <20171019200236.15892-1-jsmart2021@gmail.com>
Why can't we just switch to flush_work instead of cancel_work_sync?
fatal_err_work never requeues itself, although we might need
protection against queueing more up once we enter nvmet_ctrl_free.
next prev parent reply other threads:[~2017-10-20 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:02 [REPOST PATCH] nvmet: Fix fatal_err_work deadlock James Smart
2017-10-20 10:27 ` Christoph Hellwig [this message]
2017-10-20 14:11 ` Hannes Reinecke
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=20171020102721.GA20587@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 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.