From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: allow duplicate controller if prior controller being deleted
Date: Wed, 30 May 2018 08:06:30 +0200 [thread overview]
Message-ID: <20180530060630.GB22380@infradead.org> (raw)
In-Reply-To: <20180525210223.504-1-jsmart2021@gmail.com>
On Fri, May 25, 2018@02:02:23PM -0700, James Smart wrote:
> The current checks for whether a new controller request "matches"
> an existing controller ignores controller state and checks identity
> strings. There are cases where an existing controller may be in its
> last steps of deletion when they are "matched" by a new connection.
>
> Change the behavior so that the new connection ignores controllers
> that are deleted.
>
> Signed-off-by: James Smart <james.smart at broadcom.com>
Applied to nvme-4.18.
prev parent reply other threads:[~2018-05-30 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 21:02 [PATCH] nvme: allow duplicate controller if prior controller being deleted James Smart
2018-05-30 6:06 ` 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=20180530060630.GB22380@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;
as well as URLs for NNTP newsgroup(s).