From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
Subject: [PATCH 4.4.y] nvme: Fix managing degraded controllers
Date: Tue, 13 Feb 2018 16:50:13 +0100 [thread overview]
Message-ID: <20180213155013.GE14300@kroah.com> (raw)
In-Reply-To: <20180209213922.12644-1-keith.busch@intel.com>
On Fri, Feb 09, 2018@02:39:22PM -0700, Keith Busch wrote:
> commit 3e1e21c7bfcf upstream
That's not a commit, that is a merge point :(
> Upstream is a near rewrite of the async nvme probe that ultimately didn't
> even cleanly merge in 4.5. This patch is a much smaller change targeted
> to the regression introduced in 4.4.
>
> If a controller is in a degraded mode that needs admin assistence to
> recover, we need to leave the controller running. We just want to disable
> namespace access without shuting the controller down.
>
> Fixes: 3cf519b5a8d4("nvme: merge nvme_dev_start, nvme_dev_resume and nvme_async_probe")
>
> Cc: <stable at vger.kernel.org> # 4.4.x
> Signed-off-by: Keith Busch <keith.busch at intel.com>
Can I get a better commit id to match this up with?
thanks,
greg k-h
next prev parent reply other threads:[~2018-02-13 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 21:39 [PATCH 4.4.y] nvme: Fix managing degraded controllers Keith Busch
2018-02-13 15:50 ` Greg Kroah-Hartman [this message]
2018-02-13 16:19 ` Keith Busch
2018-02-15 14:38 ` Patch "nvme: Fix managing degraded controllers" has been added to the 4.4-stable tree gregkh
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=20180213155013.GE14300@kroah.com \
--to=gregkh@linuxfoundation.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