Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: do not block connect call on inaccessible devices
Date: Tue, 5 Jun 2018 14:51:14 +0200	[thread overview]
Message-ID: <20180605125114.GC13305@lst.de> (raw)
In-Reply-To: <20180605142318.7d566c27@pentland.suse.de>

On Tue, Jun 05, 2018@02:23:18PM +0200, Hannes Reinecke wrote:
> > > This patch inhibits partition scan if no working paths are found,
> > > and retriggers the partition scan once the device becomes active.  
> > 
> > And what updates the state once all your inaccessible or change
> > state groups become optimized?
> > 
> ANA AENs?

Not in your patch.

> Someone told me we should rely on ANA AENS or the system is hosed
> anyway :-)

Yes, of course.  But AENs aren;t going to help you if you don't
take any action upon them.

      parent reply	other threads:[~2018-06-05 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  8:29 [PATCH] nvme: do not block connect call on inaccessible devices Hannes Reinecke
2018-06-05 11:17 ` Christoph Hellwig
2018-06-05 12:23   ` Hannes Reinecke
2018-06-05 12:35     ` Bart Van Assche
2018-06-05 12:50       ` hch
2018-06-05 12:51     ` 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=20180605125114.GC13305@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