Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme-cli: Wait for device file if not present after successful add_ctrl
Date: Fri, 27 Apr 2018 15:45:26 -0600	[thread overview]
Message-ID: <20180427214526.GE5073@localhost.localdomain> (raw)
In-Reply-To: <20180427172939.3571-1-jsmart2021@gmail.com>

On Fri, Apr 27, 2018@10:29:39AM -0700, James Smart wrote:
> It's possible for the transport to return very quickly after add_ctrl
> such that the cli may attempt to access the /dev/nvme? device file
> before the udev event has propagated to user space to create the device
> file. In these cases, the open fails with EAGAIN.
> 
> As the add_ctrl call was successful, thus there "should" be a device
> file, if the open fails with EAGAIN delay 500ms and try again. Wait
> for at most 2 seconds for the device file to come into existence.
> 
> Signed-off-by: James Smart <james.smart at broadcom.com>

Applied.

      reply	other threads:[~2018-04-27 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 17:29 [PATCH] nvme-cli: Wait for device file if not present after successful add_ctrl James Smart
2018-04-27 21:45 ` Keith Busch [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=20180427214526.GE5073@localhost.localdomain \
    --to=keith.busch@intel.com \
    /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