Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-multipath: relax ANA state check
Date: Mon, 28 Jan 2019 17:30:36 +0100	[thread overview]
Message-ID: <20190128163036.GB12288@lst.de> (raw)
In-Reply-To: <20190128142446.6732-1-marting@netapp.com>

On Mon, Jan 28, 2019@07:54:46PM +0530, martinus.gpy@gmail.com wrote:
> From: Martin George <marting at netapp.com>
> 
> Always call nvme_mpath_set_live() when transitioning to a live
> state, where live is defined as ANA Optimized or Non-Optimized,
> irrespective of what the previous asymmetric access state was.
> This removes the restriction of only permitting transitions
> from states that were not considered live.

This still doesn't make sense.  We never prohibit a transition here.

What kind of problem do you see that triggered this patch?

  reply	other threads:[~2019-01-28 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 14:24 [PATCH] nvme-multipath: relax ANA state check martinus.gpy
2019-01-28 16:30 ` Christoph Hellwig [this message]
2019-01-28 17:10   ` George, Martin
2019-01-31 10:03     ` hch
  -- strict thread matches above, loose matches on Subject: below --
2019-01-25 11:12 martinus.gpy
2019-01-25 12:57 ` Hannes Reinecke
2019-01-28  7:43 ` Christoph Hellwig
2019-01-28 14:01   ` George, Martin

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=20190128163036.GB12288@lst.de \
    --to=hch@lst.de \
    /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